Asseon

4 ms·

1. 1.▲
   by Asseon 8y ago

   you are right, bad case of a Layer 8 issue.
2. 2.▲
   by Asseon 8y ago

   That does not seem to work according to ssllabs browser test.
3. 3.▲
   by Asseon 8y ago

   I was unable to find one. Right now the only way seems to be to patch nss.
4. 4.▲
   by Asseon 8y ago

   If your nginx version is 1.13 or newer than yes, that should be enough. [0] http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_p...
5. 5.▲
   by Asseon 8y ago

   Right now there are no benefits though. Because the browser sends the domainname you contact unencrypted via the TLS handshake due to SNI. So someone listing in to your communication will learn the hostname anyway. I know people are working
6. 6.▲
   by Asseon 9y ago

   Russia tried that for 3 years, now they use normal time the hole year. It seems only "summer time" is not a good idea either.
7. 7.▲
   by Asseon 11y ago

   Seems to be down here too (germany), at least the desktop client. The web client still works.
8. 8.▲
   by Asseon 11y ago

   Yes but A5/1 is utterly brocken. Besides thanks to numerous attacks possible through SS7 you probably do not even need to break the encryption.