Searched refs:alert (Results 1 – 3 of 3) sorted by relevance
6 …which will generate inputs, try to process them with the fuzz target, and alert in case of an unwa…
7738 uint8_t alert; in ssl_parse_certificate_chain() local7851 alert = MBEDTLS_SSL_ALERT_MSG_INTERNAL_ERROR; in ssl_parse_certificate_chain()7855 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_chain()7859 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in ssl_parse_certificate_chain()7861 mbedtls_ssl_send_alert_message(ssl, MBEDTLS_SSL_ALERT_LEVEL_FATAL, alert); in ssl_parse_certificate_chain()8076 uint8_t alert; in ssl_parse_certificate_verify() local8082 alert = MBEDTLS_SSL_ALERT_MSG_ACCESS_DENIED; in ssl_parse_certificate_verify()8084 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in ssl_parse_certificate_verify()8086 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_verify()8088 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_verify()[all …]
1187 * Fix bug in the alert sending function mbedtls_ssl_send_alert_message()1188 potentially leading to corrupted alert messages being sent in case1864 * Fix which alert is sent in some cases to conform to the1912 * Various changes to which alert and/or error code may be returned3321 * Fail when receiving a TLS alert message with an invalid length, or invalid3895 when sending the alert failed. The fix makes sure not to hide the error3896 that triggered the alert.3898 peer after sending a fatal alert to refuse a renegotiation attempt.3899 Previous behaviour was to keep processing data even after the alert has3916 sending the fatal alert and just drop the connection.[all …]
