Klaus Demo nginx / b157288
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. Maxim Dounin 2 years ago
1 changed file(s) with 6 addition(s) and 0 deletion(s). Raw diff Collapse all Expand all
20612061 #ifdef SSL_R_NO_SUITABLE_KEY_SHARE
20622062 || n == SSL_R_NO_SUITABLE_KEY_SHARE /* 101 */
20632063 #endif
2064 #ifdef SSL_R_NO_SUITABLE_SIGNATURE_ALGORITHM
2065 || n == SSL_R_NO_SUITABLE_SIGNATURE_ALGORITHM /* 118 */
2066 #endif
20642067 || n == SSL_R_BLOCK_CIPHER_PAD_IS_WRONG /* 129 */
20652068 || n == SSL_R_DIGEST_CHECK_FAILED /* 149 */
20662069 || n == SSL_R_ERROR_IN_RECEIVED_CIPHER_LIST /* 151 */
20822085 || n == SSL_R_UNEXPECTED_RECORD /* 245 */
20832086 || n == SSL_R_UNKNOWN_ALERT_TYPE /* 246 */
20842087 || n == SSL_R_UNKNOWN_PROTOCOL /* 252 */
2088 #ifdef SSL_R_NO_COMMON_SIGNATURE_ALGORITHMS
2089 || n == SSL_R_NO_COMMON_SIGNATURE_ALGORITHMS /* 253 */
2090 #endif
20852091 || n == SSL_R_UNSUPPORTED_PROTOCOL /* 258 */
20862092 #ifdef SSL_R_NO_SHARED_GROUP
20872093 || n == SSL_R_NO_SHARED_GROUP /* 266 */