- From: Daniel Albuschat <notifications@github.com>
- Date: Mon, 22 Oct 2018 13:44:58 -0700
- To: httpslocal/usecases <usecases@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 22 October 2018 20:45:26 UTC
You already have the home-automation use case on the list, but I'd like to reinforce this aspect. Currently, many home automation providers - be them open source such as home assistant/iobroker, or consumer gadgets like Nuki, Nest, Alexa or professional solutions (I know a few very large, German home automation manufacturers that are affected) - only allow HTTP connections, or allow HTTPS connections and take into account that the user will be presented a very dangerously looking warning by the browser (when accessed by a human) or implement HTTPS security only partially (when accessed by another machine). I think this is very unfortunate, and it's harming the "Smart Home" scenario as a whole, and I'm glad that you are working on changing this. Btw: I've written a blog post with some insights, ramblings and proposals here: https://dev.to/danielkun/where-is-https-for-iot-49ao I'd be glad if you could provide you with further information regarding requirements in smart home / IoT scenarios, if required. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpslocal/usecases/issues/1#issuecomment-431978058
Received on Monday, 22 October 2018 20:45:26 UTC