Live data from Hacker News

More awful IoT stuff

mjg59.dreamwidth.org

81–90 of 245 posts

Re: More awful IoT stuff

#81
post #69

Earlier quoted context omitted.

The network model you describe sounds just like Apple's HomeKit.

Is that compatible with non-apple devices? I generally dislike apple philosophically, so I avoid their products.

Yes, but Homekit enabled boxes need to be licensed and apparently need a custom chip.

A look at the practicalities here: http://fortune.com/2015/06/09/ceo-apple-homekit-mess/

Re: More awful IoT stuff

#82

I also mentioned this in a recent blog post: https://www.jsondata.io/blog/2016/iot-needs-a-cloud/ > Right now, the cloud - especially for IoT - isn't a healthy ecosystem. Your shiny new smart thermostat might as well be dialing into AOL on a dedicated landline. And unlike public services, these proprietary service providers lack long-term guarantees of service availability. > What we need is a push for openness and i…

>What we need is a push for openness and interoperability in the cloud

Personally I think that is the opposite of what we need. Most IoT devices should be local-network-only. So if by cloud you mean a personal cloud (local network or VPN), then yes, I agree. Otherwise keep the interwebs away from my thermostat.

Re: More awful IoT stuff

#84
post #69

Earlier quoted context omitted.

The network model you describe sounds just like Apple's HomeKit.

Is that compatible with non-apple devices? I generally dislike apple philosophically, so I avoid their products.

  > Is that compatible with non-apple devices?
Yeah, here is a list of a few products: https://support.apple.com/en-us/HT204903

Re: More awful IoT stuff

#85
post #48

Earlier quoted context omitted.

One of the reasons would be that it isn't used that often and won't allow access to your network with commodity hardware.

Isn't this idea hiding the problem though? While using uncommon hardware and protocols may thwart certain users, it's really not solving the problem of security. It's somewhat similar to the idea of using a hidden wireless network and calling that security instead of securing your network with WPA2, etc. As these devices become more popular, we'll start seeing more Zigbees and Z-wave devices become commodity hardware…

Not at all, anyone can "join" the network, but nobody can decrypt the traffic without the key.

Zigbee has built-in, easy, encryption. You simply set your router to allow unsecured joins temporarily whenever you get a new device, which then learns the key.

When the network is set to allow only secure joins only devices pre-configured with the key can see anything other than encrypted frames.

Re: More awful IoT stuff

#86
post #82

I also mentioned this in a recent blog post: https://www.jsondata.io/blog/2016/iot-needs-a-cloud/ > Right now, the cloud - especially for IoT - isn't a healthy ecosystem. Your shiny new smart thermostat might as well be dialing into AOL on a dedicated landline. And unlike public services, these proprietary service providers lack long-term guarantees of service availability. > What we need is a push for openness and i…

>What we need is a push for openness and interoperability in the cloud Personally I think that is the opposite of what we need. Most IoT devices should be local-network-only. So if by cloud you mean a personal cloud (local network or VPN), then yes, I agree. Otherwise keep the interwebs away from my thermostat.

That's a fair point, and I agree. However, the reality is that a major selling point for these things is along the lines of "control it from anywhere", and whether people actually need remote access or not, it seems that a lot of consumers still see it as a major upside.

Maybe what we really need are more consumer-friendly, self-hosted (and secure) home VPN options. That way you can just run your services on the local network, and still have remote access without opening your devices to the world (or to other companies' servers). Until the average grandma can do that, the "personal cloud" idea will probably be overshadowed by manufacturers' desire to provide proprietary remote access options, because those go hand-in-hand with things like subscription pricing models, data mining, etc.

Re: More awful IoT stuff

#87
Hold on - it sounds like this thing is running Android. Has reference to connecting with ADB, apks, and Android versions. But it's also running a SSH server and OpenWRT? What's going on there, is it running 2 different OSes for some reason, or did they somehow merge Android and OpenWRT?

Re: More awful IoT stuff

#88
post #20

Earlier quoted context omitted.

That's been my understanding as well. The cpu's used typically aren't powerful enough to do anything other than simple encryption in a reasonable amount of time. Ssl is generally out of the question. Someone please educate me if that's incorrect.

As usual, "it depends". If this thing is capable of running OpenWRT, it can run some sort of SSL for what it needs. Might be tight and might have to not be OpenSSL, but it can be done. Lesser-capable devices may have issues. But note that one way or another, the devices must speak some decent encryption to get on to WPA2 networks. Of course that's probably done in the Wifi hardware, but it still shows that it's not l…

But more to the point: there is no purpose to SSL/TLS on an appliance because it will not have a valid certificate, hence it won't protect anything. You might as well just use WPA2-PSK.

Re: More awful IoT stuff

#89
post #29

Funny timing... I just bought an LG LFXS30776S refrigerator and the first thing I noticed was that all of a sudden I had a new WiFi broadcast. Turns out that according to tech support there's no way to shut this off.

Transceiver, meet grounded aluminum foil?

Has it come to the point where your refrigerator has to wear a tinfoil hat?

Re: More awful IoT stuff

#90
post #87

Hold on - it sounds like this thing is running Android. Has reference to connecting with ADB, apks, and Android versions. But it's also running a SSH server and OpenWRT? What's going on there, is it running 2 different OSes for some reason, or did they somehow merge Android and OpenWRT?

The app is running Android, the device is OpenWRT as far as I understand.
Post reply on HN