Searched refs:alert (Results 1 – 3 of 3) sorted by relevance
7762 uint8_t alert; in ssl_parse_certificate_chain() local7875 alert = MBEDTLS_SSL_ALERT_MSG_INTERNAL_ERROR; in ssl_parse_certificate_chain()7879 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in ssl_parse_certificate_chain()7883 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in ssl_parse_certificate_chain()7885 mbedtls_ssl_send_alert_message(ssl, MBEDTLS_SSL_ALERT_LEVEL_FATAL, alert); in ssl_parse_certificate_chain()10014 uint8_t alert; in mbedtls_ssl_verify_certificate() local10020 alert = MBEDTLS_SSL_ALERT_MSG_ACCESS_DENIED; in mbedtls_ssl_verify_certificate()10022 alert = MBEDTLS_SSL_ALERT_MSG_BAD_CERT; in mbedtls_ssl_verify_certificate()10024 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in mbedtls_ssl_verify_certificate()10026 alert = MBEDTLS_SSL_ALERT_MSG_UNSUPPORTED_CERT; in mbedtls_ssl_verify_certificate()[all …]
345 alert).1618 * Fix bug in the alert sending function mbedtls_ssl_send_alert_message()1619 potentially leading to corrupted alert messages being sent in case2295 * Fix which alert is sent in some cases to conform to the2343 * Various changes to which alert and/or error code may be returned3752 * Fail when receiving a TLS alert message with an invalid length, or invalid4326 when sending the alert failed. The fix makes sure not to hide the error4327 that triggered the alert.4329 peer after sending a fatal alert to refuse a renegotiation attempt.4330 Previous behaviour was to keep processing data even after the alert has[all …]
454 core_cluster_alert: core-cluster-alert {