tree 4f12dacfe1b100e8e7165976be5a587ef823f490
parent a51a00b069e9b5cafb05c8ae48e4c2e5c08d9b13
author Maxim Dounin <mdounin@mdounin.ru> 1537873204 +0300
committer Maxim Dounin <mdounin@mdounin.ru> 1537873204 +0300

SSL: logging level of "no suitable signature algorithm".

The "no suitable signature algorithm" errors are reported by OpenSSL 1.1.1
when using TLSv1.3 if there are no shared signature algorithms.  In
particular, this can happen if the client limits available signature
algorithms to something we don't have a certificate for, or to an empty
list.  For example, the following command:

    openssl s_client -connect 127.0.0.1:8443 -sigalgs rsa_pkcs1_sha1

will always result in the "no suitable signature algorithm" error
as the "rsa_pkcs1_sha1" algorithm refers solely to signatures which
appear in certificates and not defined for use in TLS 1.3 handshake
messages.

The SSL_R_NO_COMMON_SIGNATURE_ALGORITHMS error is what BoringSSL returns
in the same situation.