Support opportunistic encryption about hyper HOT 1 OPEN

This is no longer a WIBNI, I'm upgrading it to Long-Term Goal. I'm convinced this is substantially more important for privacy and security than I previously realised.

More work needs to be done here. Ideally we want a unified way to control security policy, preferably with fine grained control. For example, users ought to be able to specify different security policy for different hosts on different schemes. This would allow users to have security policy that says something like:

1. If accessing twitter.com over HTTPS, verify certificate against a local copy, only allow strong ciphers, do not follow AltSvc recommendations; else
2. If accessing twitter.com over HTTP, use OppSec where available, verify certificate against a local copy, allow weak ciphers, follow AltSvc recommendations; else
3. If accessing any other site over HTTPS, verify certificate against local set of root CAs, only allow strong ciphers, do follow AltSvc recommendations; else
4. If accessing any other site over HTTP, use OppSec where available, do not perform cert verification, allow weak ciphers, follow AltSvc recommendations.

This form of fine-grained security policy is useful, but we need to have an intelligent API and intelligent defaults. Again, most users won't need this so they should fall into a pit of success, with secure default values and behaviours. Users who do want it should be able to set extremely fine-grained security policy.

A further benefit would be to have detailed documentation about how to use the security policy tools. This should provide users with a good idea of what actions strengthen security, what actions weaken security, and what you gain/lose in functionality when performing those actions.

from hyper.