Timeline for Disabling SSL v2 and weak ciphers on client PC's
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 13:14 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Jul 15, 2013 at 2:36 | history | edited | TildalWave | CC BY-SA 3.0 |
added 504 characters in body
|
| Jul 15, 2013 at 2:06 | comment | added | David Hoelzer | Two quick points. First, you should expect that the server will attempt to negotiate up to the highest common cipher/protocol supported. This should, hopefully, take you to TLS/1.2. Second, requiring that browsers disable SSLv2 won't matter so much when they connect to you but your users may hate you when they try to connect to the many thousands of sites who have not yet moved to TLS. I know, it's been years, but until people get bitten (or a PCI auditor sits on them for TLS/1.2) they don't seem to react. | |
| Jul 15, 2013 at 1:55 | history | answered | TildalWave | CC BY-SA 3.0 |