From: travankor <travankor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openvpn: add mbedtls build option.
Date: Fri, 10 Jul 2020 23:46:45 +0200 [thread overview]
Message-ID: <20200710214645.y-woT-PGMWfKM9lLbu-tFkUrSfYK7n8acsueNMYGoEw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23429@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
New comment by travankor on void-packages repository
https://github.com/void-linux/void-packages/pull/23429#issuecomment-656906045
Comment:
`mbedtls` is officially supported by openvpn. This should be 100% interoperable with other openvpn instances. (Some trivia: This version of openvpn was sponsored by the Dutch government for their restricted communication channels.)
The features that don't work compared to the openssl build:
```
* PKCS#12 file support
* --capath support - Loading certificate authorities from a directory
* Windows CryptoAPI support
* X.509 alternative username fields (must be "CN")
```
This is why the `mbedtls` and `pkcs12` options conflict since the build fails with both turned on.
---
Admittedly, I don't know the reason why libressl is causing problems and to what extent things are broken with openvpn. And yes, I tested protonovpn, which seems to work.
next prev parent reply other threads:[~2020-07-10 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 22:37 [PR PATCH] " travankor
2020-07-07 0:29 ` travankor
2020-07-07 8:35 ` mobinmob
2020-07-07 13:57 ` jkoderu-git
2020-07-10 16:11 ` Johnnynator
2020-07-10 16:54 ` ericonr
2020-07-10 21:46 ` travankor [this message]
2020-07-11 0:48 ` travankor
2020-07-11 1:29 ` ericonr
2020-07-11 1:56 ` travankor
2020-07-12 11:44 ` [PR PATCH] [Merged]: " Johnnynator
2020-07-14 10:47 ` Redcroft
2020-07-14 11:39 ` ericonr
2020-07-14 11:39 ` 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=20200710214645.y-woT-PGMWfKM9lLbu-tFkUrSfYK7n8acsueNMYGoEw@z \
--to=travankor@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).