Skip to main content
11 events
when toggle format what by license comment
Jul 18, 2023 at 17:56 comment added Moshe For any future visitors: See RFC 9113 section 9.2.2. TLS 1.2 Cipher Suites, httpwg.org/specs/rfc9113.html#tls12ciphers which references Appendix A, a list of unallowed cipher suites: httpwg.org/specs/rfc9113.html#BadCipherSuites
May 16, 2016 at 1:56 answer added DIYGUY timeline score: 1
Mar 21, 2016 at 13:51 comment added Yet Another User @SteffenUllrich ssl_prefer_server_ciphers says otherwise AFAIK.
Mar 21, 2016 at 6:01 comment added Steffen Ullrich The way the TLS handshake works you don't need to find it because it will find itself if you just allow enough secure ciphers on the server side.
Mar 20, 2016 at 22:06 comment added Yet Another User @SteffenUllrich I realised I misread the spec. It doesn't prohibit offering insecure ciphers... it just doesn't allow negotiation of one. So, basically, I need to find the least insecure one supported by clients.
Mar 20, 2016 at 16:47 comment added Steffen Ullrich You need an overlap of a single cipher suite between client and server. It is not a problem if the server offers lots of (secure) cipher suites so that it can pick one which is offered by the client. The server can also support ciphers which are not offered by the client. Don't restrict yourself unnecessarily at the server side.
Mar 20, 2016 at 15:59 comment added Yet Another User @SteffenUllrich Yes, but there's a giant blacklist that makes the page not load in compliant browsers. This has very minimal overlap with the pre-tls 1.2 suites.
Mar 20, 2016 at 7:25 comment added Steffen Ullrich There is no special cipher suite needed for HTTP/2 but your server but support the HTTP/2 protocol. See wiki.mozilla.org/Security/… for useful configuration examples regarding ciphers.
Mar 20, 2016 at 7:23 answer added dsign timeline score: 1
Mar 20, 2016 at 7:16 review First posts
Mar 20, 2016 at 7:38
Mar 20, 2016 at 7:11 history asked Yet Another User CC BY-SA 3.0