News for hackers. Stuff that matters.
Re:Overlock – IoT Exception Tracking by dordoka on Thursday November 16, 2017 @10:03AM (#15713126)
Congratulations on your beta launch! Really interesting.

Some questions: FAQ reads that channel from devices to Overlock employs MQTT(S). I guess that means MQTT-SN, using TLS layer for authentication. Which auth methods do you support? Do you support validation of the client and the server? Can the gateway act as such also for Overlock or do devices need to open the MQTT channel directly?

Re:Overlock – IoT Exception Tracking by bitdivision on Thursday November 16, 2017 @10:38AM (#15713493)
Thanks!

That should probably be written as secure-MQTT, I'll get that changed. So we are just using vanilla MQTT over TLS.

We're currently using token-based authentication but certainly open to supporting other options. Did you have any suggestions?

I'm not quite sure what you mean about validation? In general, the gateway will already be in communication with the end devices over whatever protocol they're using. So it makes sense to log state etc. from the gateway for those devices. In that sense, the gateway does act as a gateway for overlock.