IPv6 readyNote: This archive passes through spamassassin. Every mail marked with the subject "*****SPAM*****" has exceed a certain threshold of spam-like behaviour.

Re: [Users] Freeswan Proposal Syntax

From: Sam Sgro (sam_at_freeswan.org)
Date: Mon May 13 2002 - 22:56:36 CEST


-----BEGIN PGP SIGNED MESSAGE-----

On Mon, 13 May 2002, Myner, Josh wrote:

> -------- Original Message --------
> Subject: Re: VPN conundrum
> Date: Tue, 31 Jul 2001 07:38:51 -0400
> From: "Frank Paxhia" <paxhia_at_us.ibm.com>
> To: Tom Harding <tomh_at_thinlink.com>
>
> Yes, sorry I haven't gotten back to you since then. I've analyzed the
> traces and the problem is definitely caused by freeS/WAN sending
> (initiating) the first proposal with proposal number "0". According
> to my IKE expert, this was brought up at one of the town meetings at the
> VPN bakeoffs. The recommendation from the IKE authors was to not use or
> start with this value. We have this hardcoded resulting in the error
> message you see. Starting in V5R1 we've added additional logic to
> tolerate certain situations like this, but, they are predicated on other
> conditions - mostly security related.

Take a look at doc/interop.html; you'll find information on how to make
FreeS/WAN work with the AS/400 by starting with proposal #1.

Sam Sgro.
sam_at_freeswan.org

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: For the matching public key, finger the Reply-To: address.

iQCUAwUBPOAoh0OSC4btEQUtAQEKnAP4ssO9RBVcfS5BgyWtfp9SdcQmX9yvyygI
5jeW1qN4FoNbbT+EwVZ+NbtbccBba9LsDWLtJA7gtJ15e9DMu6qNupyTxm5JAAiR
r9EQ7dUl7kwTp40T/BaB8X5Dyao17muYAXznRxcRzVgH88xVNKM/7N1cwMKbS/Q+
kG90GTtz1w==
=4HQT
-----END PGP SIGNATURE-----

_______________________________________________
Users mailing list
Users_at_lists.freeswan.org
http://lists.freeswan.org/mailman/listinfo/users



This archive was generated by hypermail 2.1.3 : Mon Jul 29 2002 - 05:19:58 CEST