Timeline for Qualys SSL Scan weak cipher suites which are secure according to ciphersuite.info
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 8:14 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Jan 26, 2021 at 1:26 | history | edited | dave_thompson_085 | CC BY-SA 4.0 |
hack markdown so list items with years are correct, and fix a few typos
|
| Jan 25, 2021 at 22:51 | history | edited | kelalaka | CC BY-SA 4.0 |
added 80 characters in body
|
| Jan 25, 2021 at 21:18 | comment | added | user163495 | Yes, you can use TLS_AES_*_GCM_SHA256/384 in TLS 1.2 as well. | |
| Jan 25, 2021 at 16:25 | history | edited | kelalaka | CC BY-SA 4.0 |
added the GCM TLS 1.2 and come clarifications, too.
|
| Jan 25, 2021 at 16:16 | comment | added | kelalaka | @MechMK1 The GCM is aslo defined for TLS 1.2 in RFC 5288. If this is the case, one should restrict the cipher suites. | |
| Jan 25, 2021 at 15:16 | comment | added | user163495 | I'd generally agree, but not every client is TLS 1.3 compatible | |
| Jan 25, 2021 at 14:57 | history | answered | kelalaka | CC BY-SA 4.0 |