Hacker News new | past | comments | ask | show | jobs | submit login

You may be right, but you’ve said nothing to support your position.

Most of HN mistakenly assumes IoT == putting cameras and microphones on televisions with no security (eg, super stoopidity), when in fact IoT is a powerful way for businesses to monitor/diagnose/control remote devices (like jet engines, vending machines, stop lights,...)

But I don’t see what Mozilla has to do with that, nor why we need some kind of “gateway” or json spec when it’s just yet another internet device.




Please don't connect jet engines to the internet and use a REST API to control them.


Haha

Actually of course it’s about collecting data for predictive maintenance and to help in making design improvements.


Yeah, that's when things work well. But soon someone finds a use-after-free in that code et voilà now he has full control[1] over the engine.

[1] OK, maybe not full control over the engine because that's not how it works, but it has full control over the embedded monitoring system, which is still pretty bad.


> jet engines, vending machines, stop lights

IoT means different devices connecting to internet and/or each other. A jet engine is part of a closed system, there is no need to use a standard protocol to communicate to it. You don't just pick one and plug into a multi-million-dollar plane. Vending machines need no special protocols to connect to other things, because why would they? And stop lights. These things may connect to some server or maybe each other, but no standard protocol is needed, if a traffic light isn't supposed to talk to a random device passing by (and it isn't supposed to).


Stop lights might want to have some 1-n beacon protocol available for automated cars, and vending machines likewise might want a way to expose what's currently in stock and allow sufficient verbs to pay by a phone app.

These don't necessarily need to be the same system, only one might need interactivity, but there's certainly a case to be made that both devices could reasonably want to communicate with passers-by.


The traffic lights communicating with vehicles automated or not is sinister. That would get attacked ASAP, DoS or otherwise, and crashes would happen. A vending machine provides a keyboard interface for making selections. You can integrate NFC to it and require the payment in between the selection and dispensing. Allowing automated connections to public devices is not a useful idea.


Right so, we agree, special protocols and json specs for "IoT" don't make any sense, since the last thing we need in our home is every product we buy transmitting on the internet.

A gateway to block all those devices, that could be useful.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: