OpenVPN
|
This section describes how OpenVPN peers generate and exchange key material necessary for the security operations performed on data channel packets.
The key generation and exchange process between OpenVPN client and server occurs every time data channel security parameters are negotiated, for example during the initial setup of a VPN tunnel or when the active security parameters expire. In source code terms, this is when a new key_state structure is initialized.
OpenVPN supports two different ways of generating and exchanging key material between client and server. These are known as key method 1 and key method 2. Key method 2 is the recommended method. Both are explained below.
There are two methods for generating key data when using key method 2 the first is OpenVPN's traditional approach that exchanges random data and uses a PRF and the other is using the RFC5705 keying material exporter to generate the key material. For both methods the random data is exchange but only used in the traditional method.
Key method 2 key expansion is performed by the generate_key_expansion_openvpn_prf()
function. Please refer to its source code for details of the key expansion process.
When the client sends the IV_PROTO_TLS_KEY_EXPORT flag and the server replies with key-derivation tls-ekm
the RFC5705 key material exporter with the label EXPORTER-OpenVPN-datakeys is used for the key data.
OpenVPN uses the either the OpenSSL library or the mbed TLS library as its source of random material.
In OpenSSL, the RAND_bytes()
function is called to supply cryptographically strong pseudo-random data. The following links contain more information on this subject:
RAND_bytes()
function: http://www.openssl.org/docs/crypto/RAND_bytes.htmlIn mbed TLS, the Havege random number generator is used. For details, see the mbed TLS documentation.
The key exchange process is initiated by the OpenVPN process running in client mode. After the initial three-way handshake has successfully completed, the client sends its share of random material to the server, after which the server responds with its part. This process is depicted below:
Client Client Server Server State Action Action State ---------- -------------------- -------------------- ---------- ... waiting until three-way handshake complete ... S_START S_START key_method_?_write() send to server --> --> --> --> receive from client S_SENT_KEY key_method_?_read() S_GOT_KEY key_method_?_write() receive from server <-- <-- <-- <-- send to client key_method_?_read() S_SENT_KEY S_GOT_KEY ... waiting until control channel fully synchronized ... S_ACTIVE S_ACTIVE
For more information about the client and server state values, see the Control Channel Processor module.
Depending on which key method is used, the ? in the function names of the diagram above is a
1
or a 2
. For example, if key method 2 is used, that key exchange would be started by the client calling key_method_2_write()
. These functions are called from the Control Channel Processor module's tls_process()
function and control the key generation and exchange process as follows:
key_method_2_write()
: generate random material locally, and if in server mode generate key expansion.key_method_2_read()
: read random material received from remote peer, and if in client mode generate key expansion.The OpenVPN client and server communicate with each other through their control channel. This means that all of the data transmitted over the network, such as random material for key generation, is encapsulated in a TLS layer. For more details, see the Control Channel TLS module documentation.