but will the work you have accomplished, enable me to at least communicate with my controller or the endpoint at Trifork?
I have already written this somewhere, even several times, but okay, once again.
Devices in SecureDeviceGrid communicate over an encrypted channel. All the communication is normally done via Grid cloud. The procedure is the following:
- Alice establishes encrypted connection to the Grid and asks the Grid to forward her to Bob. The Grid’s application-level protocol (let’s call it Grid Control) is based on Google’s Protobuf.
- The Grid (given Bob is online) responds “OK” and issues some one-time identifier (let’s say XXX).
- Alice creates second connection to the Grid, but instead of establishing encrypted channel, says “Forward me to XXX”. At this point the Grid will ask Bob if he knows Alice and wants to talk (Bob maintains control connection to be able to do that). After the Grid has responded “Ok”, Alice it’s talking to the Grid any more, but to Bob. At this point an encrypted channel is established, and Alice and Bob use their own application-level protocol to exchange data.
The encryption protocol, used by the “new” mdglib, used by newer devices, is a custom protocol, based on CurveCP. This is what OpenSDG implements.
LivingConnect does not use this encryption protocol. It looks like it uses standard SSL instead. Grid servers support both, looks like they autodetect, but of course LivingConnect device itself won’t recognize the new encryption procotol. That’s the main difference.
So, you can take my library and replace custom encryption protocol with SSL. I remember Christian was able to connect to the Grid this way. Control Protocol is expected to be the same, so you’ll be able to ask the Grid to connect you to your device. I don’t think device’s application-level protocol would be the same as “Dominion” (original name, extracted from APKs), used by DeviSmart and Icon.
If you want, i have a cloned copy of Christian’s repository with disassembled LinkCC app, i can share it with you. You’ll be able to study embedded mdglib lua code and also understand application-level protocol from the app itself.