News for hackers. Stuff that matters.
Re:More awful IoT stuff by DougN7 on Wednesday June 22, 2016 @05:40PM (#11957238)
I've been debating about hooking my garage door opener up using a built-in feature so I could open the door from my iPhone. I don't trust that whatever central site I'll be connected to is safe. If I _knew_ the vendor had implemented your protocol/software well, and I _knew_ your software was safe, yeah, I'd use it. But I don't know those two things, so no way am I hooking my home's door up to the Internet...
Re:More awful IoT stuff by nbadg on Wednesday June 22, 2016 @08:01PM (#11957985)
In my case you actually do know that the vendor is using the protocol. You would have to be running the protocol on (in this example) your iPhone in order to talk to it. Everything is client-side verified and enforced by encryption.

You wouldn't have any guarantee that the garage door opener isn't also running a separate web connection in the background, but arguably unless you're actively monitoring your LAN (or just plain radio) traffic you don't have that anyways.

Put a different way, you can't prevent your manufacturer from, for example, adding a SIM card and wireless connection to your garage door opener. At some point you have to trust them.

Re:More awful IoT stuff by DougN7 on Thursday June 23, 2016 @11:03AM (#11961461)
When you say I'd have to be running the protocol, wouldn't I really be running their garage door opener app? In other words, how do I know your protocol is being used?
Re:More awful IoT stuff by nbadg on Thursday June 23, 2016 @12:14PM (#11962126)
If they were using the protocol, they have two options:

1. Roll their own implementation (highly discouraged). Increase their development burden. Introduce higher maintenance burden. Slightly more flexibility for app deployment. And run the risk of my company disallowing interoperable embedded commercial implementations out of security concerns for the users. Basically, at this point the company is better off not using the protocol.

2. Use our implementation (Hypergolix). Massively decrease development and maintenance burden. They now have an install dependency, though, so distribution is a bit more complicated. Significant reduction in time and money invested in the app.

The critical point is this: with option 1, you're correct in that you don't know the protocol is in use, but it's extremely likely that they wouldn't be using it here, nor advertise that they were. With option two, you know that they are using it, because you have to manually install the application to run the protocol.

Re:More awful IoT stuff by DougN7 on Thursday June 23, 2016 @01:18PM (#11962714)
With #2 do I know they are using your additional install? Would your app indicate their app was a registered client and was sending commands through it?
Re:More awful IoT stuff by nbadg on Thursday June 23, 2016 @02:45PM (#11963422)
It certainly could, as it has full knowledge of what's connected. That's quite a ways down the road though; for now we're focusing on Razpi <-> computer. Mobile deployment is much more complicated (also a much larger market though).
Re:More awful IoT stuff by wcummings on Wednesday June 22, 2016 @06:05PM (#11957398)
Still probably more secure than most remote garage door openers tbh