2 ms·
What key size and cipher suite are you using? (If you're willing to post the URL, we can have a much more informed discussion, but a sanitized copy of an SSL La
by geofft 11y ago
What key size and cipher suite are you using? (If you're willing to post the URL, we can have a much more informed discussion, but a sanitized copy of an SSL Labs test or even of `openssl s_client -connect localhost:443` is also workable.)
Also, what hardware are you using? This site is aimed more at companies who fear of losing business because their site is slow, than people hosting a blog on a home server; if you don't have hardware-accelerated crypto (like most server-class machines have, whether or not you explicitly looked for it) its argument is less valid.
- Ono-Sendai 11y agoI'm using all the defaults, as provided by LibTLS, so I'm not sure. I'll have a poke round and tell you later. The TLS support is not deployed to the internet so posting a URL wouldn't be very helpful. Hardware is my Ivy bridge i7 with 4 physical cores.
- geofft 11y agoYeah, Ivy Bridge is new enough. Are you negotiating an AES-GCM suite? Also, are you using a 2048-bit key if you're doing RSA? (A larger key almost certainly provides no more security, since your intermediate is almost certainly 2048-bit, and will noticeably slow down handshakes.)
- Ono-Sendai 11y agoLibTLS tells me what was negotiated was 'ECDHE-RSA-CHACHA20-POLY1305' Edit: some more output: New, TLSv1/SSLv3, Cipher is ECDHE-RSA-CHACHA20-POLY1305 Server public key is 1024 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-CHACHA20-POLY1305