Re: [Openvpn-devel] Re: openvpn server in client-to-client mode

2004-12-22 Thread James Yonan
On Tue, 21 Dec 2004, Charles Duffy wrote: > On Tue, 21 Dec 2004 21:09:21 +0100, Tor HÃ¥kon Gjerde wrote: > > > It doesn't sound that hard to make that patch. If someone would be so kind > > and send me one, I would be very grateful. > > Presuming that you aren't a coder yourself -- it typically

Re: [Openvpn-devel] Re: Fwd: openvpn config parsing

2004-12-22 Thread Alberto Gonzalez Iniesta
On Wed, Dec 22, 2004 at 05:11:51AM -0700, James Yonan wrote: > On Wed, 22 Dec 2004, Charles Duffy wrote: > > > On Wed, 22 Dec 2004 11:00:09 +0100, Alberto Gonzalez Iniesta wrote: > > > Recent updates of openvpn appear to have changed the handling of > > > whitespace in tls certificate names. > >

Re: [Openvpn-devel] Re: Fwd: openvpn config parsing

2004-12-22 Thread James Yonan
On Wed, 22 Dec 2004, Charles Duffy wrote: > On Wed, 22 Dec 2004 11:00:09 +0100, Alberto Gonzalez Iniesta wrote: > > Recent updates of openvpn appear to have changed the handling of > > whitespace in tls certificate names. > ... > > Now it needs '_' not '.' for spaces: > > My guess is that this

[Openvpn-devel] Re: Fwd: openvpn config parsing

2004-12-22 Thread Charles Duffy
On Wed, 22 Dec 2004 11:00:09 +0100, Alberto Gonzalez Iniesta wrote: > Recent updates of openvpn appear to have changed the handling of > whitespace in tls certificate names. ... > Now it needs '_' not '.' for spaces: My guess is that this is a consequence of some string-handling changes that wer

[Openvpn-devel] Fwd: openvpn config parsing

2004-12-22 Thread Alberto Gonzalez Iniesta
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