From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenVPN - DEPRECATED OPTION: --tls-remote
Date: Mon, 11 Aug 2014 11:36:37 +0200 [thread overview]
Message-ID: <1407749797.2114.31.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <F61CE3BE-3664-4181-8388-78ABA154D00A@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
Hi Erik,
On Tue, 2014-07-29 at 20:05 +0200, ummeegge wrote:
> Hi all,
> since the update to OpenVPN version 2.3 on IPFire the client log
> message "DEPRECATED OPTION: --tls-remote, please update your
> configuration" appears. so the clientside directive "--tls-remote"
> will be removed from OpenVPN in one of the comming versions -->
> https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage . For
> future updates of OpenVPN on IPFire (2.4+) it will be important to
> modify existing client.ovpn´s and replace the "--tls-remote name" with
> the new "--verify-x509-name name type" directive.
Yes, we should do this at some point. The question that is currently on
my mind is if that is completely backwards-compatible with all
installations that we do have out there.
> Since OpenVPN client/server version 2.3.2 the new verify option can be
> used in client configs whereby "type" includes the possibilty of 3
> different kinds of verification --> "subject", "name" and
> "name-prefix" . This leads to a question which one of the "types"
> should be used for future versions on IPFire.
> At this time IPFire handles "--tls-remote" automatically and it can´t
> be configured over the WUI, this is handy cause the user doesn´t need
> to bother around with all that kind of settings, but should this
> remain in that way also for the new verification method ?
This should not be configurable for the user, because I cannot see the
point right now. It should stay compatible to what we are doing at the
moment.
> Also, to use "--verify-x509-name" the clients needs to have a version
> >= 2.3.2 otherwise the connection won´t come up so there is no
> backwards compatibility with the new directive and version =< 2.3.1 .
This is my biggest concern as there might be many systems that run old
versions.
> May some people out there have some ideas, informations, ...., for
> this topic ?
Not really as far as we can see. Would you please update the code for
this and send patches when you have the time for it?
> Anyway a discussion about that might be interesting.
-Michael
next parent reply other threads:[~2014-08-11 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F61CE3BE-3664-4181-8388-78ABA154D00A@ipfire.org>
2014-08-11 9:36 ` Michael Tremer [this message]
2014-08-11 15:44 ` 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=1407749797.2114.31.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--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