The local system was configured tosupport the cipher suites permitted for domestic use. The remote systemwas configured to support only the cipher suites permitted for exportuse.

The remote system was configuredto support the cipher suites permitted for domestic use. The localsystem was configured to support only the cipher suites permitted forexport use.

The local and remote systems shareno cipher suites in common. This can be due to a misconfiguration ateither end. It can be due to a server being misconfigured to use anon-RSA certificate with the RSA key exchange algorithm.

This error has many potentialcauses; for example:

Certificate or key not found in database.

Certificate not marked trusted indatabase and Certificate's issuer not marked trusted in database.

Wrong password for keydatabase.

Missing database.

A certificate was received fromthe remote system and was passed to the certificate authenticationcallback function provided by the local application. That callbackfunction returned SECFailure, and the bad certificate callbackfunction either was not configured or did not choose to override theerror code returned by the certificate authentication callback function.

This error code should occur onlyon sockets that are acting as servers. It is a generic error, used whennone of the other more specific error codes defined in this file applies.

This error code should occur onlyon sockets that are acting as clients. It is a generic error, used whennone of the other more specific error codes defined in this file applies.

The operation encountered acertificate that was not one of the well known certificate types handledby the certificate library.

On a client socket, this means theremote server has attempted to negotiate the use of a version of SSLthat is not supported by the NSS library, probably an invalid versionnumber. On a server socket, this means the remote client has requestedthe use of a version of SSL older than version 2.

This error code should be returnedby the certificate authentication callback function when it detects thatthe Common Name in the remote server's certificate does not match thehostname sought by the local client, according to the matching rulesspecified for CERT_VerifyCertName.

The remote server has asked to useSSL version 2, and SSL version 2 is disabled in the local client'sconfiguration.

This usually indicates that theclient and server have failed to come to agreement on the set of keysused to encrypt the application data and to check message integrity. Ifthis occurs frequently on a server, an active attack (such as the'million question' attack) may be underway against the server.

The remote system has reportedthat it received a message with a bad Message Authentication Code fromthe local system. This may indicate that an attack on that server isunderway.

The remote system has received acertificate from the local system, and has rejected it for some reason.

The remote system has received acertificate from the local system, and has determined that thecertificate has been revoked.

The remote system has received acertificate from the local system, and has determined that thecertificate has expired.

The local socket is configured insuch a way that it cannot use any of the SSL cipher suites. Possiblecauses include: (a) both SSL2 and SSL3 are disabled, (b) All theindividual SSL cipher suites are disabled, or (c) the socket isconfigured to handshake as a server, but the certificate associated withthat socket is inappropriate for the Key Exchange Algorithm selected.

The local system and the remotesystem are in different FORTEZZA domains. They must be in the samedomain to communicate.

The application has attempted toconfigure SSL to use an unknown cipher suite.

Possible causes: (a) all ciphersuites have been configured to be disabled, (b) the only cipher suitesthat are configured to be enabled are those that are disallowed bycipher export policy, (c) the socket is configured to handshake as aserver, but the certificate associated with that socket is inappropriatefor the Key Exchange Algorithm selected.

SSL was using a Block cipher, andthe last block in an SSL record had incorrect padding information in it.This usually indicates that the client and server have failed to cometo agreement on the set of keys used to encrypt the application dataand to check message integrity. If this occurs frequently on a server,an active attack (such as the 'million question' attack) may beunderway against the server.

This generally indicates that theremote peer system has a flawed implementation of SSL, and is violatingthe SSL specification.

This error should never occur. Ifit does, it indicates a flaw in the NSS SSL library.

The local socket received an SSL3alert record from the remote peer, reporting that the remote peer haschosen to end the connection. The receipt of this alert is an error onlyif it occurs while a handshake is in progress.

On a client socket, this errorreports that the remote server has failed to perform an 'SSL Step down'for an export cipher. It has sent a certificate bearing a domestic-gradepublic key, but has not sent a ServerKeyExchange message containing anexport-grade public key for the key exchange algorithm. Such aconnection cannot be permitted without violating U.S. export policies.On a server socket, this indicates a failure of the local library.

An SSL client has requested an SSLcipher suite that uses a Key Exchange Algorithm for which the localserver has no appropriate public key. This indicates a configurationerror on the local server.

A cryptographic operation requiredto complete the handshake failed because the token that was performingit was removed while the handshake was underway. Another token may alsohave been inserted into the same slot.

A cryptographic operation requireda PKCS#11 token with specific abilities, and no token could be found inany slot, including the 'soft token' in the internal virtual slot, thatcould do the job. May indicate a server configuration error, such ashaving a certificate that is inappropriate for the Key ExchangeAlgorithm selected.

Received a malformed (too longor short or invalid content) SSL handshake:

All the error codes in thefollowing block indicate that the local socket received an improperlyformatted SSL3 handshake message from the remote peer. This probablyindicates a flaw in the remote peer's implementation.

Received a malformed (too longor short) SSL record:

All the error codes in thefollowing block indicate that the local socket received an improperlyformatted SSL3 record from the remote peer. This probably indicates aflaw in the remote peer's implementation.

Received an SSL handshake thatwas inappropriate for the current state:

All the error codes in thefollowing block indicate that the local socket received an SSL3handshake message from the remote peer at a time when it wasinappropriate for the peer to have sent this message. For example, aserver received a message from another server. This probably indicates aflaw in the remote peer's implementation.

Received an SSL record that wasinappropriate for the current state:

All the error codes in thefollowing block indicate that the local socket received an SSL3 recordfrom the remote peer at a time when it was inappropriate for the peer tohave sent this message. This probably indicates a flaw in the remotepeer's implementation.

Received record/message withunknown discriminant:

All the error codes in thefollowing block indicate that the local socket received an SSL3 recordor handshake message from the remote peer that it was unable tointerpret because the byte that identifies the type of record or messagecontained an unrecognized value. This probably indicates a flaw in theremote peer's implementation.

Received an alert report:

All the error codes in thefollowing block indicate that the local socket received an SSL3 or TLSalert record from the remote peer, reporting some issue that it had withan SSL record or handshake message it received. (Some _Alertcodes are listed in other blocks.)

Unspecified errors thatoccurred while attempting some operation:

All the error codes in thefollowing block describe the operation that was being attempted at thetime of the unspecified failure. These failures may be caused by thesystem running out of memory, or errors returned by PKCS#11 routinesthat did not provide meaningful error codes of their own. These shouldrarely be seen. (Certain of these error codes have more specificmeanings, as described.)

After the data to be sent wasencrypted, the attempt to send it out the socket failed. Likely causesinclude that the peer has closed the connection.

On a client socket, indicates afailure of the PKCS11 key generation function. On a server socket,indicates a failure of one of the following: (a) to unwrap thepre-master secret from the ClientKeyExchange message, (b) to derive themaster secret from the premaster secret, (c) to derive the MAC secrets,cryptographic keys, and initialization vectors from the master secret.If encountered repeatedly on a server socket, this can indicate that theserver is actively under a 'million question' attack.

or improper or corrupted data.