Timeline for Identify and disable weak cipher suites
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2019 at 10:05 | answer | added | Luke | timeline score: 0 | |
| Aug 27, 2018 at 22:35 | history | edited | YLearn | CC BY-SA 4.0 |
Clean up preformatted text, removed unnecessary text, and some capitilization
|
| S Aug 27, 2018 at 20:10 | history | suggested | R1W | CC BY-SA 4.0 |
correct some mistake
|
| Aug 27, 2018 at 15:51 | review | Suggested edits | |||
| S Aug 27, 2018 at 20:10 | |||||
| Jan 29, 2015 at 15:58 | answer | added | bryan | timeline score: -2 | |
| Jan 21, 2015 at 4:07 | answer | added | Anti-weakpasswords | timeline score: 0 | |
| Jan 21, 2015 at 3:55 | answer | added | Kevin | timeline score: 0 | |
| Jan 10, 2014 at 8:39 | vote | accept | DonQi | ||
| Jan 9, 2014 at 19:28 | history | tweeted | twitter.com/#!/StackSecurity/status/421362841812471809 | ||
| Jan 9, 2014 at 18:04 | comment | added | Steve | Also, the MSDN page is a bit deceptive in that you don't need to use code to remove/modify any. You can use GPEdit as specified at the top of the page. Just remove any cipher suites you don't want from the list. Though @gowenfawr's linked tool looks pretty handy in this scenario. | |
| Jan 9, 2014 at 17:03 | comment | added | i0null | Typical recommendation is to supporting only 128 bit or greater ciphers, but this depends on required browser support. Avoiding RC4 won't harm either. | |
| Jan 9, 2014 at 14:29 | review | First posts | |||
| Jan 9, 2014 at 15:18 | |||||
| Jan 9, 2014 at 14:24 | answer | added | gowenfawr | timeline score: 30 | |
| Jan 9, 2014 at 14:18 | history | edited | DonQi | CC BY-SA 3.0 |
corrected spelling
|
| Jan 9, 2014 at 14:12 | history | asked | DonQi | CC BY-SA 3.0 |