5 ms·
I think the solution is much simpler: don't put an open web server in your dishwasher, and use standard authenticated, encrypted channels between the applicatio
by microcolonel 10y ago
I think the solution is much simpler: don't put an open web server in your dishwasher, and use standard authenticated, encrypted channels between the application and the appliance so that at least only somebody with credentials can use your dishwasher an espionage device.
And failing that, some Good Old All-American Common Law suits should do the industry a world of good. This product surely has an implied warranty of some kind.
- tinus_hn 10y agoWhat provides standard encrypted channels? Why would such a service not have vulnerabilities?
- beaconstudios 10y agoI'm guessing they meant TLS for comms and SSH/VPN for authentication.
- norea-armozel 10y agoOr even simpler: don't put any kind of writable software/firmware on the dishwasher in the first place. Beyond maybe some scheduled washing options, why does a dishwater need to be IoT'd? Seriously, I think all this is meant to pad the price of the appliances rather than give users an actual working product.
- dom0 10y agoThis is a professional machine. See https://www.miele.de/professional/grossraum-reinigungs-und-desinfektionsautomaten-560.htm?mat=10339600&name=PG_8528 https://www.miele.de/professional/grossraum-reinigungs-und-d... Having an API totally makes sense here to have monitoring and error reporting.
- norea-armozel 10y agoI can totally see something like that needing full programmatic capability, but anything consumer grade should be read-only in terms of functionality. A refrigerator in my home kitchen doesn't need an API to maintain temperature within an acceptable range vs electrical consumption where as a warehouse refrigerator does (like those that might be part of a smart grid agreement to give over control to utilities with a price discount as a benefit).