ssl(3) - Manual pages

DESCRIPTION

The OpenSSL ssl library implements the Transport Layer Security (TLS v1) protocols.

At first the library must be initialized; see SSL_library_init(3).

Then an SSL_CTX object is created as a framework to establish TLS/SSL enabled connections (see SSL_CTX_new(3)). Various options regarding certificates, algorithms, etc., can be set in this object.

When a network connection has been created, it can be assigned to an SSL object. After the SSL object has been created using SSL_new(3), SSL_set_fd(3) or SSL_set_bio(3) can be used to associate the network connection with the object.

Then the TLS/SSL handshake is performed using SSL_accept(3) or SSL_connect(3) respectively. SSL_read(3) and SSL_write(3) are used to read and write data on the TLS/SSL connection. SSL_shutdown(3) can be used to shut down the TLS/SSL connection.

DATA STRUCTURES

Currently the OpenSSL ssl library functions deal with the following data structures:

SSL_METHOD (SSL Method): That's a dispatch structure describing the internal ssl library methods/functions which implement the various protocol versions. It's needed to create an SSL_CTX. See TLS_method(3) for constructors.
SSL_CIPHER (SSL Cipher): This structure holds the algorithm information for a particular cipher which is a core part of the SSL/TLS protocol. The available ciphers are configured on an SSL_CTX basis and the actually used ones are then part of the SSL_SESSION.
SSL_CTX (SSL Context): That's the global context structure which is created by a server or client once per program lifetime and which holds mainly default values for the SSL structures which are later created for the connections.
SSL_SESSION (SSL Session): This is a structure containing the current TLS/SSL session details for a connection: SSL_CIPHERs, client and server certificates, keys, etc.
SSL (SSL Connection): That's the main SSL/TLS structure which is created by a server or client per established connection. This actually is the core structure in the SSL API. At run-time the application usually deals with this structure which has links to mostly all other structures.

HEADER FILES

Currently the OpenSSL ssl library provides the following C header files containing the prototypes for the data structures and functions:

ssl.h: That's the common header file for the SSL/TLS API. Include it into your program to make the API of the ssl library available. It internally includes both more private SSL headers and headers from the crypto library. Whenever you need hardcore details on the internals of the SSL API, look inside this header file.
ssl2.h: That's the sub header file dealing with the SSLv2 protocol only.

Usually you don't have to include it explicitly because it's already included by ssl.h.
ssl3.h: That's the sub header file dealing with the SSLv3 protocol only.
Usually you don't have to include it explicitly because it's already included by ssl.h.
ssl23.h: That's the sub header file dealing with the combined use of the SSLv2 and SSLv3 protocols.
Usually you don't have to include it explicitly because it's already included by ssl.h.
tls1.h: That's the sub header file dealing with the TLSv1 protocol only.
Usually you don't have to include it explicitly because it's already included by ssl.h.