2 ms·
It annoys me to no end when the SSL/TLS connection is hidden behind a click. Joe user is asked -- taught -- to trust an http page without knowing what protocol
by pasbesoin 17y ago
It annoys me to no end when the SSL/TLS connection is hidden behind a click. Joe user is asked -- taught -- to trust an http page without knowing what protocol the resulting request will use nor whether the recipient is verified.
I set the browser to notify when transitioning from https to http. Then I try to force a site to give me an https connection before I start entering sensitive data. If the browser pops a protocol transition warning, I back out.
It also annoys me when an https delivered page in turn pulls in http content. This breaks the security of the entire rendered page. Having the user check for the https protocol in the address bar is not sufficient.
It seems to me that the basic concepts involved are not that difficult (leaving out the math). Don't start communicating until you know the "channel" is secure and the other endpoint is verified. Verification is accomplished through a chain of trust. Pages are composed of multiple pieces. If any piece/participant in the channel comes from an unsecured or unverified source, you must treat the channel as compromised.
But no browser presents them in a clear and meaningful fashion, with enough context to describe plainly to the average user what is going on.