I was just wondering if someone could tell me how TLS 1.3 affects tls cipher priority and negotiation on the control channel in openvpn 2.4.6? I have an openVPN 2.4.6 server, compiled with OpenSSL 1.1.1, which includes full support for tls 1.3. On one of my 2.4.6 clients (also using openssl 1.1.1), I changed the[code]tls-version-min[/code] option from 1.2 to 1.3. In this client config, I already had it set to prioritise the ChaCha20-Poly1305 tls cipher with the option [code]tls-cipher TLS-ECDHE-ECDSA-WITH-CHACHA20-POLY1305-SHA256[/code] in addition to tls-version-min This was working fine. On the client, it would connect with [code]TLSv1.2, cipher TLSv1.2 TLS-ECDHE-ECDSA-WITH-CHACHA20-POLY1305-SHA256[/code] However, since updating the client to [code]tls-version-min 1.3[/code], it now connects using [code]Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384[/code] even though the tls-cipher is still set to use chacha20. Does tls 1.3 negate the affects of including [code]tls-cipher[/code] option? How do I use ChaCha20-Poly1305 on tls 1.3?

[quote=TinCanTech post_id=81458 time=1537872721 user_id=37053] You are welcome to submit a bug report but I expect the developers are aware of the problem. [/quote] I went ahead and submitted [url=https://community.openvpn.net/openvpn/ticket/1118#ticket]a bug ticket[/url], just in case. I didn't realise 2.4.6 didn't officially support 1.3. Hope it can be worked in to openvpn some time soon.

TLS 1.3 cipher priority

jimdoe

I was just wondering if someone could tell me how TLS 1.3 affects tls cipher priority and negotiation on the control channel in openvpn 2.4.6?

I have an openVPN 2.4.6 server, compiled with OpenSSL 1.1.1, which includes full support for tls 1.3.

On one of my 2.4.6 clients (also using openssl 1.1.1), I changed the

tls-version-min

option from 1.2 to 1.3.

In this client config, I already had it set to prioritise the ChaCha20-Poly1305 tls cipher with the option

tls-cipher TLS-ECDHE-ECDSA-WITH-CHACHA20-POLY1305-SHA256

in addition to tls-version-min

This was working fine. On the client, it would connect with

TLSv1.2, cipher TLSv1.2 TLS-ECDHE-ECDSA-WITH-CHACHA20-POLY1305-SHA256

However, since updating the client to

tls-version-min 1.3

, it now connects using

Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384

even though the tls-cipher is still set to use chacha20.

Does tls 1.3 negate the affects of including

tls-cipher

option? How do I use ChaCha20-Poly1305 on tls 1.3?

jimdoe

Just an addition. I noticed on the openssl wiki that with tls 1.3, the way that ciphersuites are defined is different, and now no longer differentiates between the certificate type (ECDSA, RSA etc). This means that the way ciphesuites are presented is different now, especially the way in which it is written when adding it to the config. However, even after adding the new definition of ChaCha20-Poly1305 to the tls-cipher in the ovpn client config:

tls-cipher TLS_CHACHA20_POLY1305_SHA256

I still can only make a TLS_AES_256_GCM_SHA384 connection when using tls 1.3.

From my limited understanding of the openssl wiki, does this mean openvpn itself needs an update to properly configure how it presents the supported ciphers and their priority when using 1.3? Perhaps I should file a bug? (Although I really have no idea if this is a bug or just a feature of tls 1.3)

TinCanTech

I tested this and found the same.

Currently, OpenVPN does not officially support TLS 1.3, it is still a work in progress.
You are welcome to submit a bug report but I expect the developers are aware of the problem.

jimdoe

TinCanTech wrote You are welcome to submit a bug report but I expect the developers are aware of the problem.

I went ahead and submitted a bug ticket, just in case.
I didn't realise 2.4.6 didn't officially support 1.3. Hope it can be worked in to openvpn some time soon.