Unencrypted HTTP is already open to MITM attacks. What I proposed was using self-signed certificates in conjunction with certificate pinning, which means that as long as your first connection to a website isn't MITMed, later connections cannot be MITMed or snooped on. As for the compression, I was referring to LZMA for header compression. I am well aware of implementation efforts of LZMA in Firefox and Chrome.
What we need is some form or decentralised certificate authority, i have no idea how that could work though.
DNSSEC could be used to distribute certificates: https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Na...
Re:HTTP 2.0
by jimktrains2 on Tuesday July 09, 2013 @09:09PM
(#6016796)
Isn't DNSSEC still have centralized certs for the tlds?
HTTP allready supports LZMA, its just the browser and web servers that dont. If a browser sent the header:
instead of: and the server supported it, it would "just work". Unfortunately none of the major browsers or server have implemented it.