How does a client (like SSLLabs) know all the cipher suites a server supports if the server doesn’t send its list of supported cipher suites?

I was looking at the TLS handshake and I noticed that the client will send its list of supported cipher suites and the server will select a cipher suite. The server never sends its list of supported cipher suites. How does a … Continue reading How does a client (like SSLLabs) know all the cipher suites a server supports if the server doesn’t send its list of supported cipher suites?

Why RSA is used in TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ciphersuite [duplicate]

I try to understand where the signature is used in TLS 1.2.
The ciphersuite of google.com is TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256. However, if I look at the certificate, I can find an ECDSA key but the signature algorithm is RSA. So I’m wondering what is the purpose of ECDSA ?

I know that ECDHE parameters are sent in a separate TLS message. ECDSA is perhaps used to sign these parameters with ECDSA ?

Also, can you confirm that if TLS_ECDH_ECDSA_WITH_xxx is used, ECDH parameters are not in the certificate but in a separate message right ?

Continue reading Why RSA is used in TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ciphersuite [duplicate]

Debug OpenSSL connection from client to resolve ‘no shared cipher’ problem in Dovecot

I’m migrating Dovecot from an Ubuntu 14.04 server to Debian 9. All good apart from one client using Entourage 2008 which now no longer works – my dovecot log reports:

failed: error:1417A0C1:SSL routines:tls_post_process_clie… Continue reading Debug OpenSSL connection from client to resolve ‘no shared cipher’ problem in Dovecot