Open fpietrosanti opened 11 years ago
Now that GlobaLeaks is going to implement HTTPS internally it would be interesting to implement this feature there as well, in particular for the fact that for security reasons we would like to disable TLSv1 but for compatibility reason we are forced to keep it up for showing messages about the supported browsers alternatives.
In order to let TorHS have a better understanding of the security context of the Client accessing it via Tor2web, Tor2web proxy should advise with an appropriate HTTP Header the SSL/TLS cipher negotiated by the client.
For example a TorHS operator may be willing to accept only Web clients that negotiated Forward Secrecy enabled ciphers.
The header maybe something like X-Tor2web-Cipher: Name_Of_SSL_Cipher.
This issue is related to #56