Re:Deprecating Non-Secure HTTP
by tyho on Thursday April 30, 2015 @08:05PM
(#9468446)
What features have to do with encryption is this. If a browser asks a user "Do you want http://example.com to be able to access your camera", what it is really asking is "Do you want http://example.com, anybody on your local network, state actors, anybody between you and example.com, people who can mess around with BGP and your DNS provider to be able to access your camera?". TLS mostly makes the first question more truthful.
[ Parent
| on HN ]
Re:Deprecating Non-Secure HTTP
by bashinator on Thursday April 30, 2015 @08:12PM
(#9468484)
You might explicitly include "employees of the coffee shop/hotel/library providing wifi" in the list of actors who can intercept your traffic. Honestly, I think that one will get the most attention of the average person.
And perhaps most importantly of all, your employer/school.
Re:Deprecating Non-Secure HTTP
by walterbell on Thursday April 30, 2015 @09:06PM
(#9468726)
Who can intercept SSL traffic.
Re:Deprecating Non-Secure HTTP
by icebraining on Thursday April 30, 2015 @09:28PM
(#9468821)
Only if they also control the PC or you allow them to install certificates. You can still safely use their network with your own device(s).
If they require proxy and root cert installation. They can do whatever they please.