News for hackers. Stuff that matters.
Re:ARM Mbed IoT Device Platform by officialchicken on Saturday February 20, 2016 @08:08PM (#11142804)
Insecurity of things... by default, the connection is insecure [1][2] and unencrypted. But at least they're starting to move in the right direction [3], if you have a commercial license.

[1] https://docs.mbed.com/docs/mbed-client-guide/en/latest/Howto...

[2] https://docs.mbed.com/docs/mbed-client-guide/en/latest/api/c...

[3] https://github.com/ARMmbed/mbedtls

*edit: formatting

Re:ARM Mbed IoT Device Platform by DyslexicAtheist on Tuesday February 23, 2016 @07:46PM (#11163623)
1. The link you provided is about LWM2M Security Object, not about how the mbed client connects to mbed Device Connector (https://connector.mbed.com/).

2. To get a better feeling on how a device would actually connect to the server, here's an easy to follow example: https://github.com/ARMmbed/mbed-client-linux-example - this can be built & run on an Ubuntu machine. (Note: there are some prerequisities, as explained in https://github.com/ARMmbed/mbed-client-linux-example/blob/ma...)

3. You can see in main.cpp (https://github.com/ARMmbed/mbed-client-linux-example/blob/ma...) that we're using certificate mode (line 128), and that's also on free accounts

Re:ARM Mbed IoT Device Platform by IshKebab on Sunday February 21, 2016 @11:02AM (#11144972)
mBed TLS is Apache 2. You don't need a commercial license.