Re: Intent to deprecate: Insecure HTTP

> > Note that Firefox does not presently support either DANE or DNSSEC, > so we don't need to distinguish these. > > -Ekr > Nor does Chrome, and look what happened to both browsers... http://www.zdnet.com/article/google-banishes-chinas-main-digital-certificate-authority-cnnic/ ...the keys to

Re: Intent to deprecate: Insecure HTTP

I think that you'll need to define a number of levels of security, and decide how to distinguish them in the Firefox GUI: - Unauthenticated/Unencrypted [http] - Unauthenticated/Encrypted [https ignoring untrusted cert warning] - DNS based auth/Encrypted[TLSA certificate hash in DNS] - Ditto