cipher vs tls-ciphersuite

This forum is for admins who are looking to build or expand their OpenVPN setup.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
tonyhawk
OpenVpn Newbie
Posts: 1
Joined: Fri Aug 04, 2023 12:31 am

cipher vs tls-ciphersuite

Post by tonyhawk » Fri Aug 04, 2023 12:48 am

I'm currently using the -tls-ciphersuite (tls 1.3) command on server to only allow the cipher I want (TLS_AES_256_GCM_SHA384) but there is the command -cipher too, i am looking to confirm if the below response is still valid for TLS 1.3 and --tls-ciphersuite

Do I need to use -tls-ciphersuite + -cipher to make sure I only use AES-256-GCM to encrypt the connection?

I'm on OpenVPN 2.4.7

Below is a response from 2015 by Steffan Karger.


'Modern' OpenVPN (2.x, using the TLS mode) basically sets up two connections:
  • The 'control channel'. This is a low bandwidth channel, over which e.g. network parameters and key material for the 'data channel' is exchanged'. OpenVPN uses TLS to protect control channel packets.
  • The 'data channel'. This is the channel over which the actual VPN traffic is sent. This channel is keyed with key material exchanged over the control channel.

Both these channels are duplexed over a single TCP or UDP port.

--tls-cipher controls the cipher used by the control channel. --cipher together with --auth control the protection of the data channel.

And regarding security, OpenVPN uses encrypt-then-mac for its data channel, rather than mac-then-encrypt like TLS. All the CBC-related issues you hear about are due to the combination mac-then-encrypt + CBC. This means that AES-CBC for the data channel is perfectly fine from a security perspective.

(And there is no GCM support for the data channel yet. That will arrive in OpenVPN 2.4.)

Post Reply