From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Possible Bug in OVPN
Date: Wed, 24 Aug 2016 00:23:34 -0500 [thread overview]
Message-ID: <57BD2F56.4010108@dailydata.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
Problem exists in 103 (and I'm not sure how much further back), but I
just noticed it.
When creating the client package, the .ovpn file has the following line:
verify-x509-name my.server.name name
(my.server.name is actually the server's name). The error message is:
Options error: Unrecognized option or missing parameter(s) in
rodolico-TO-IPFire.ovpn:13: verify-x509-name (2.2.1)
This line is not recognized by OpenVPN v2.2.1, which is on my Debian
Wheezy workstation. It appears to also be a problem with tunnelblick
(see
https://groups.google.com/forum/#!topic/tunnelblick-discuss/R6gY0C-CgfY). This
command appeared in OpenVPN v2.3, so anyone using versions prior to that
will not be able to use the configuration file.
The syntax before used the deprecated tls-remote, ie
tls-remote my.server.name
Which works on Windows (OpenVPN GUI), Linux (OpenVPN) and OSX (tunnelblick).
Let me know if you want me to file a bug report. However, for release
104, I'd recommend either leaving the verify-x509-name out, or using the
old (deprecated) tls-remote (which still works under v2.3, from what
I've seen, though it is deprecated as per
https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage)
However, if you just want it documented (it is a deprecated flag which
will be fully removed in 2.4), let me know and I'll put it in the wiki.
Rod
--
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
next reply other threads:[~2016-08-24 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 5:23 R. W. Rodolico [this message]
2016-08-25 16:20 ` ummeegge
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=57BD2F56.4010108@dailydata.net \
--to=rodo@dailydata.net \
--cc=development@lists.ipfire.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