SSL Alert messages

Alert messages, as in the following sample, are documented in RFC 2246 (http://www.ietf.org/rfc/rfc2246.txt).

ERROR read_v3_alert(): SSL V3 alert 46 received from <ip> ERROR
gsk_secure_socket_init(): SSL V3 server handshake failed with ...INFO 
default_setsocketoptions(): TCP_NODELAY restored for socket ...EXIT 
gsk_secure_socket_init(): <—- Exit status 0x0000019e (414)
       ENTRY gsk_strerror(): 
—->  Thd-0 EXIT gsk_strerror(): <—- Exit status 0x00000000 (0)

Alert	Description	Explanation
0	`close_notify`	This message notifies the recipient that the sender will not send any more messages on this connection. The session cannot resume if any connection is terminated without proper `close_notify` messages with level equal to warning.
10	`unexpected_message`	An inappropriate message was received. This alert is always indicates an unrecoverable error and should never be observed in communication between proper implementations.
20	`bad_record_mac`	This alert is returned if a record is received with an incorrect MAC. This message always indicates an unrecoverable error.
21	`decryption_failed`	A `TLSCiphertext` decrypted in an invalid way. Either it was not an even multiple of the block length or its padding values, when checked, were not correct. This message always indicates an unrecoverable error.
22	`record_overflow`	A `TLSCiphertext` record was received which had a length more than 2^14+2048 bytes, or a record decrypted to a `TLSCompressed` record with more than 2^14+1024 bytes. This message always indicates an unrecoverable error.
30	`decompression_failure`	The decompression function received improper input (for example, data that would expand to excessive length). This message always indicates an unrecoverable error.
40	`handshake_failure`	Receiving of a `handshake_failure` alert message indicates that the sender was unable to negotiate an acceptable set of security parameters with the available options. This is an unrecoverable error.
41	? no_certificate ?	See SSL support.
42	`bad_certificate`	A certificate was corrupt, contained signatures that did not verify correctly, or had other problems.
43	`unsupported_certificate`	A certificate was of an unsupported type.
44	`certificate_revoked`	A certificate was revoked by its signer.
45	`certificate_expired`	A certificate has expired or is not currently valid.
46	`certificate_unknown`	Some other (unspecified) issue arose in processing the certificate, rendering it unacceptable.
47	`illegal_parameter`	A field in the handshake was out of range or inconsistent with other fields. This always indicates an unrecoverable error.
48	`unknown_ca`	A valid certificate chain or partial chain was received, but the certificate was not accepted because the CA certificate could not be located or could not be matched with a known, trusted CA. This message always indicates an unrecoverable error.
49	`access_denied`	A valid certificate was received, but when access control was applied, the sender decided not to proceed with negotiation. This message always indicates an unrecoverable error.
50	`decode_error`	A message could not be decoded because some field was out of the specified range or the length of the message was incorrect. This message always indicates an unrecoverable error.
51	`decrypt_error`	A handshake cryptographic operation failed, including being unable to correctly verify a signature, decrypt a key exchange, or validate a finished message.
60	`export_restriction`	A negotiation not in compliance with export restrictions was detected. For example, attempting to transfer a 1024 bit ephemeral RSA key for the `RSA_EXPORT` handshake method. This message always indicates an unrecoverable error.
70	`protocol_version`	The protocol version the client has attempted to negotiate is recognized, but not supported. (For example, old protocol versions might be avoided for security reasons.) This message always indicates an unrecoverable error.
71	`insufficient_security`	Returned instead of `handshake_failure` when a negotiation has failed specifically because the server requires ciphers more secure than those supported by the client. This message always indicates an unrecoverable error.
80	`internal_error`	An internal error unrelated to the peer or the correctness of the protocol makes it impossible to continue (such as a memory allocation failure). This message always indicates an unrecoverable error.
90	`user_canceled`	This handshake is being canceled for some reason unrelated to a protocol failure. If the user cancels an operation after the handshake is complete, just closing the connection by sending a `close_notify` is more appropriate. This alert should be followed by a `close_notify`. This message is generally a warning.
100	`no_renegotiation`	Sent by the client in response to a hello request or by the server in response to a client hello after initial handshaking. Either of these would normally lead to renegotiation. When renegotiation is not appropriate, the recipient should respond with this alert. At that point, the original requester can decide whether to proceed with the connection. One case where this would be appropriate would be where a server has spawned a process to satisfy a request; the process might receive security parameters (key length, authentication, and so forth) at startup, and it might be difficult to communicate changes to these parameters after that point. This message is always a warning.