Searched refs:alert (Results 1 – 3 of 3) sorted by relevance
2383 uint8_t alert; in ssl_parse_certificate_chain() local2501 alert = MBEDTLS_SSL_ALERT_MSG_INTERNAL_ERROR; in ssl_parse_certificate_chain()2505 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_chain()2509 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in ssl_parse_certificate_chain()2511 mbedtls_ssl_send_alert_message( ssl, MBEDTLS_SSL_ALERT_LEVEL_FATAL, alert ); in ssl_parse_certificate_chain()2743 uint8_t alert; in ssl_parse_certificate_verify() local2749 alert = MBEDTLS_SSL_ALERT_MSG_ACCESS_DENIED; in ssl_parse_certificate_verify()2751 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in ssl_parse_certificate_verify()2753 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_verify()2755 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_verify()[all …]
6 …which will generate inputs, try to process them with the fuzz target, and alert in case of an unwa…
280 * Fix which alert is sent in some cases to conform to the1726 * Fail when receiving a TLS alert message with an invalid length, or invalid2300 when sending the alert failed. The fix makes sure not to hide the error2301 that triggered the alert.2303 peer after sending a fatal alert to refuse a renegotiation attempt.2304 Previous behaviour was to keep processing data even after the alert has2321 sending the fatal alert and just drop the connection.3297 * Some example server programs were not sending the close_notify alert.3683 * Some example server programs were not sending the close_notify alert.3806 * Sending of security-relevant alert messages that do not break
