Hi, yet another report on feature changes not documented.
I thought this may be related to --key-method 2 only, but it seems to be
the same on --key-method 1. Has this changed some where in the 2.x
development? In that case, we should document this for old users.
Thanks.
----- Forwarded message from Ron <r...@debian.org> -----
From: Ron <r...@debian.org>
To: Alberto Gonzalez Iniesta <a...@inittab.org>
Subject: openvpn config parsing
List-Post: openvpn-devel@lists.sourceforge.net
Date: Fri, 10 Dec 2004 12:09:42 +1030
X-CRM114-Version: 20040816.BlameClockworkOrange-auto.3 (regex: TRE 0.6.8)
MF-A10FFB4C
X-CRM114-Status: Good ( pR: 0.9831 )
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham
version=3.0.1
X-Spam-Level:
Hi Alberto,
Recent updates of openvpn appear to have changed the handling
of whitespace in tls certificate names.
ie. for:
Subject: C=Oz, ST=Secured, L=Zone, O=Riviera tunnel, OU=uoa VPN client,
CN=twain.riviera.oz/emailAddress=keymaster@oz
I used to need:
tls-remote
/C=Oz/ST=Secured/L=Zone/O=Riviera.tunnel/OU=uoa.VPN.client/CN=twain.riviera.oz/emailAddress=keymaster@oz
Now it needs '_' not '.' for spaces:
tls-remote
/C=Oz/ST=Secured/L=Zone/O=Riviera_tunnel/OU=uoa_VPN_client/CN=twain.riviera.oz/emailAddress=keymaster@oz
This might be worth a mention in the readme, it broke my
existing setup 'silently' -- though it might have been easier
to find if I didn't run off chasing red herrings based on prior
upgrade breakages first :-)
Anyway, thanks for maintaining this one, speaking as an old time
user of cipe, this really is a very nice 'next step' in that
problem space.
best,
Ron
----- End forwarded message -----
--
Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico
agi@(inittab.org|debian.org)| en GNU/Linux y software libre
Encrypted mail preferred | http://inittab.org
Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3
