[Openswan dev] Re: [Openswan Users] ANNOUNCE: New Release Candidates: 1.0.4rc1 and 2.1.2rc4

Ken Bantoft ken at xelerance.com
Sat May 8 14:26:25 CEST 2004


You're now the 2nd to report it.  Looks like we've got a bug in the cert 
sending code... back out to 2.1.2rc3, and we'll see about fixing it and 
issuing an rc5 shortly.


On Sat, 8 May 2004, Juha Pietikäinen wrote:

> Hi,
> 
> I just updated my Openswan from v2.1.2rc3 to v2.1.2rc4. I can't establish
> IPsec/L2TP connection anymore between Windows XP client running native
> microsoft IPsec/L2TP and Fedora Core 1 with l2tpd v0.69. Windows XP gives
> error 790: The L2TP connection attempt failed because certificate validation
> on the remote computer failed.
> 
> Server side logs doesn't show anything strange.
> 
> I have tried with both leftsendcert= flag and leftsendcert= always, without
> success.
> 
> By the way, version number seems to be still v2.1.2rc3 after the update.
> 
> Juha Pietikäinen
> 
> 
> ----- Original Message ----- 
> From: "Ken Bantoft" <ken at xelerance.com>
> To: <dev at lists.openswan.org>; <users at lists.openswan.org>
> Sent: Friday, May 07, 2004 7:19 PM
> Subject: [Openswan Users] ANNOUNCE: New Release Candidates: 1.0.4rc1 and
> 2.1.2rc4
> 
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> >
> > Hi folks,
> >
> > I've pushed new RC's for both the 1.x and 2.x trees out to the
> > web+ftpsites - http://www.openswan.org/code
> >
> >
> > Changes:
> >
> > 1.x Branch:
> > Openswan 1.0.4rc1
> > * Fix for 64bit 3DES errors (kb)
> > * Fix for NAT-T Floating Port (mlafon/pw)
> > * snprintf and /proc changes (dhr/ts/kb)
> >
> > 2.x Branch:
> > Openswan v2.1.2rc4
> > * Fix loading of 2.6 modules
> > * Fix for snprintfs() in /proc, new for 2.4.25 kernels (dhr/pw)
> > * Fix checks for some log files/dirs in case they are sockets or pipes
> (pw)
> > * Fix for crl.pem crash/core (dhr/as/kb)
> > * Fix corruption of some /proc files (dhr/kb)
> > * Fix leftsendcert= flag.  You probably want this =always if you are doing
> >   X.509 connections and having problems with no ID/Key found errors.
> >

-- 
Ken Bantoft			VP Business Development
ken at xelerance.com		Xelerance Corporation
sip://toronto.xelerance.com	http://www.xelerance.com

The future is here. It's just not evenly distributed yet. 
        -- William Gibson




More information about the Dev mailing list