From: jkoderu-git <jkoderu-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openvpn build with libressl-3.1.3 does not connect
Date: Sun, 12 Jul 2020 13:38:12 +0200 [thread overview]
Message-ID: <20200712113812.aMaaHsjFnmQ_8E_D6S609pwe1QmLCM0PVSnLGGjkxzo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23413@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
New comment by jkoderu-git on void-packages repository
https://github.com/void-linux/void-packages/issues/23413#issuecomment-657210078
Comment:
I found the problem, hopefully no need to switch to openssl.
Openvpn with Libressl 3.1.3 negotiate TLS1.3 but after Protonvpn servers force their TLS1.2 ciphers with option `ncp-ciphers`. The problem is use of TLS1.2 ciphers in a TLS1.3 connection.
On the libressl 3.1.1 changelog:
```
Improved cipher suite handling to automatically include TLSv1.3 cipher
suites when they are not explicitly referred to in the cipher string.
```
To reproduce download the .ovpn from protonvpn and add `tls-version-max 1.2`. I don't know with protonvpn-cli, I modified template.ovpn and connenct.ovpn but it resets to its options. Though I recommend protonvpn-cli for dns leak protecion.
next prev parent reply other threads:[~2020-07-12 11:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 11:39 [ISSUE] " jkoderu-git
2020-07-06 13:03 ` Johnnynator
2020-07-06 13:26 ` TinCanTech
2020-07-06 16:15 ` jkoderu-git
2020-07-06 18:13 ` TinCanTech
2020-07-06 18:27 ` ericonr
2020-07-06 18:58 ` jkoderu-git
2020-07-08 14:43 ` Johnnynator
2020-07-08 15:06 ` TinCanTech
2020-07-08 17:44 ` jkoderu-git
2020-07-10 13:40 ` HadetTheUndying
2020-07-10 15:55 ` TinCanTech
2020-07-10 15:57 ` TinCanTech
2020-07-10 15:57 ` TinCanTech
2020-07-10 15:58 ` Johnnynator
2020-07-10 16:02 ` TinCanTech
2020-07-10 16:04 ` HadetTheUndying
2020-07-10 16:07 ` Johnnynator
2020-07-10 16:09 ` Johnnynator
2020-07-10 16:29 ` TinCanTech
2020-07-11 13:25 ` mvf
2020-07-12 10:54 ` jkoderu-git
2020-07-12 11:38 ` jkoderu-git [this message]
2020-07-12 17:03 ` HadetTheUndying
2020-07-12 17:26 ` jkoderu-git
2020-08-17 15:06 ` HadetTheUndying
2020-08-17 15:07 ` HadetTheUndying
2020-08-22 12:45 ` jkoderu-git
2020-08-22 13:33 ` jkoderu-git
2020-08-22 13:33 ` jkoderu-git
2021-01-21 17:54 ` ericonr
2021-01-22 9:46 ` travankor
2021-01-22 9:47 ` travankor
2021-01-22 13:12 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200712113812.aMaaHsjFnmQ_8E_D6S609pwe1QmLCM0PVSnLGGjkxzo@z \
--to=jkoderu-git@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).