=over 4

=over 4

the operation was completely successfully.

the operation was completely successfully.

an error occurred parsing the command options.

an error occurred parsing the command options.

one of the input files could not be read.

one of the input files could not be read.

an error occurred creating the CMS file or when reading the MIME

an error occurred creating the CMS file or when reading the MIME

message.

message.

an error occurred decrypting or verifying the message.

an error occurred decrypting or verifying the message.

the message was verified correctly but an error occurred writing out

the message was verified correctly but an error occurred writing out

the signers certificates.

the signers certificates.

=over 4

=over 4

the operation was completely successfully.

the operation was completely successfully.

an error occurred parsing the command options.

an error occurred parsing the command options.

one of the input files could not be read.

one of the input files could not be read.

an error occurred creating the PKCS#7 file or when reading the MIME

an error occurred creating the PKCS#7 file or when reading the MIME

message.

message.

an error occurred decrypting or verifying the message.

an error occurred decrypting or verifying the message.

the message was verified correctly but an error occurred writing out

the message was verified correctly but an error occurred writing out

the signers certificates.

the signers certificates.

=over 4

=over 4

The TSA client computes a one-way hash value for a data file and sends

The TSA client computes a one-way hash value for a data file and sends

the hash to the TSA.

the hash to the TSA.

The TSA attaches the current date and time to the received hash value,

The TSA attaches the current date and time to the received hash value,

signs them and sends the time stamp token back to the client. By

signs them and sends the time stamp token back to the client. By

creating this token the TSA certifies the existence of the original

creating this token the TSA certifies the existence of the original

data file at the time of response generation.

data file at the time of response generation.

The TSA client receives the time stamp token and verifies the

The TSA client receives the time stamp token and verifies the

signature on it. It also checks if the token contains the same hash

signature on it. It also checks if the token contains the same hash

an application specific error. This will never be returned unless explicitly

an application specific error. This will never be returned unless explicitly

set by an application.

set by an application.

=head1 NOTES

=head1 NOTES

The above functions should be used instead of directly referencing the fields

The above functions should be used instead of directly referencing the fields

=over 4

=over 4

The operation succeeded.

The operation succeeded.

The operation failed. Check the error queue to find out the reason.

The operation failed. Check the error queue to find out the reason.

=over 4

=over 4

 The operation failed. In case of the add operation, it was tried to add

 The operation failed. In case of the add operation, it was tried to add

 the same (identical) session twice. In case of the remove operation, the

 the same (identical) session twice. In case of the remove operation, the

 session was not found in the cache.

 session was not found in the cache.

 The operation succeeded.

 The operation succeeded.

=over 4

=over 4

The operation failed because B<CAfile> and B<CApath> are NULL or the

The operation failed because B<CAfile> and B<CApath> are NULL or the

processing at one of the locations specified failed. Check the error

processing at one of the locations specified failed. Check the error

stack to find out the reason.

stack to find out the reason.

The operation succeeded.

The operation succeeded.

=over 4

=over 4

The operation succeeded.

The operation succeeded.

A failure while manipulating the STACK_OF(X509_NAME) object occurred or

A failure while manipulating the STACK_OF(X509_NAME) object occurred or

the X509_NAME could not be extracted from B<cacert>. Check the error stack

the X509_NAME could not be extracted from B<cacert>. Check the error stack

=over 4

=over 4

The length B<sid_ctx_len> of the session id context B<sid_ctx> exceeded

The length B<sid_ctx_len> of the session id context B<sid_ctx> exceeded

the maximum allowed length of B<SSL_MAX_SSL_SESSION_ID_LENGTH>. The error

the maximum allowed length of B<SSL_MAX_SSL_SESSION_ID_LENGTH>. The error

is logged to the error stack.

is logged to the error stack.

The operation succeeded.

The operation succeeded.

=over 4

=over 4

The new choice failed, check the error stack to find out the reason.

The new choice failed, check the error stack to find out the reason.

The operation succeeded.

The operation succeeded.

connection will fail with decryption_error before it will be finished

connection will fail with decryption_error before it will be finished

completely.

completely.

PSK identity was not found. An "unknown_psk_identity" alert message

PSK identity was not found. An "unknown_psk_identity" alert message

will be sent and the connection setup fails.

will be sent and the connection setup fails.

=over 4

=over 4

The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been

The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been

established.

established.

The TLS/SSL handshake was not successful but was shut down controlled and

The TLS/SSL handshake was not successful but was shut down controlled and

by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the

by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the

=over 4

=over 4

The SSL_clear() operation could not be performed. Check the error stack to

The SSL_clear() operation could not be performed. Check the error stack to

find out the reason.

find out the reason.

The SSL_clear() operation was successful.

The SSL_clear() operation was successful.

=over 4

=over 4

The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been

The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been

established.

established.

The TLS/SSL handshake was not successful but was shut down controlled and

The TLS/SSL handshake was not successful but was shut down controlled and

by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the

by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the

=over 4

=over 4

The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been

The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been

established.

established.

The TLS/SSL handshake was not successful but was shut down controlled and

The TLS/SSL handshake was not successful but was shut down controlled and

by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the

by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the

The read operation was successful; the return value is the number of

The read operation was successful; the return value is the number of

bytes actually read from the TLS/SSL connection.

bytes actually read from the TLS/SSL connection.

The read operation was not successful. The reason may either be a clean

The read operation was not successful. The reason may either be a clean

shutdown due to a "close notify" alert sent by the peer (in which case

shutdown due to a "close notify" alert sent by the peer (in which case

=over 4

=over 4

A new session was negotiated.

A new session was negotiated.

A session was reused.

A session was reused.

=over 4

=over 4

The operation failed. Check the error stack to find out why.

The operation failed. Check the error stack to find out why.

The operation succeeded.

The operation succeeded.

=over 4

=over 4

The operation failed; check the error stack to find out the reason.

The operation failed; check the error stack to find out the reason.

The operation succeeded.

The operation succeeded.

=over 4

=over 4

No shutdown setting, yet.

No shutdown setting, yet.

=over 4

=over 4

The shutdown was successfully completed. The "close notify" alert was sent

The shutdown was successfully completed. The "close notify" alert was sent

and the peer's "close notify" alert was received.

and the peer's "close notify" alert was received.

The shutdown is not yet finished. Call SSL_shutdown() for a second time,

The shutdown is not yet finished. Call SSL_shutdown() for a second time,

if a bidirectional shutdown shall be performed.

if a bidirectional shutdown shall be performed.

The write operation was successful, the return value is the number of

The write operation was successful, the return value is the number of

bytes actually written to the TLS/SSL connection.

bytes actually written to the TLS/SSL connection.

The write operation was not successful. Probably the underlying connection

The write operation was not successful. Probably the underlying connection

was closed. Call SSL_get_error() with the return value B<ret> to find out,

was closed. Call SSL_get_error() with the return value B<ret> to find out,

Return values from the server callback are interpreted as follows:

Return values from the server callback are interpreted as follows:

=item > 0

=item > 0

PSK identity was found and the server callback has provided the PSK

PSK identity was found and the server callback has provided the PSK

PSK identity was not found. An "unknown_psk_identity" alert message

PSK identity was not found. An "unknown_psk_identity" alert message

will be sent and the connection setup fails.

will be sent and the connection setup fails.

=cut

=cut