Date: Fri, 31 Jan 2003 23:07:18 +0100 (CET) From: Helge Oldach <stable31jan03@oldach.net> To: sam@errno.com (Sam Leffler) Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: fast ipsec committed Message-ID: <200301312207.h0VM7Ih6030847@sep.oldach.net> In-Reply-To: <100c01c2c973$9e7decf0$52557f42@errno.com> from Sam Leffler at "Jan 31, 2003 1:56:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Sam Leffler: > > diff -r /usr/include/net/pfkeyv2.h /mnt/usr/include/net/pfkeyv2.h > > 1c1 > > < /* $FreeBSD: src/sys/net/pfkeyv2.h,v 1.4.2.4 2003/01/24 05:11:33 sam Exp > $ */ > > --- > > > /* $FreeBSD: src/sys/net/pfkeyv2.h,v 1.4.2.3 2001/10/24 19:49:13 ume Exp > $ */ > > 303,305c303,305 > > < #define SADB_AALG_MD5HMAC 2 > > < #define SADB_AALG_SHA1HMAC 3 > > < #define SADB_AALG_MAX 251 > > --- > > > #define SADB_AALG_MD5HMAC 1 /*2*/ > > > #define SADB_AALG_SHA1HMAC 2 /*3*/ > > > #define SADB_AALG_MAX 8 > > > Yes, I missed this in my commit. I should revert pfkeyv2.h's constants to > maintain binary compatibility. Unfortunately this will require another > rebuild of racoon. Sorry. Never mind. My intention was just to warn the list about this side effect. It will affect -STABLE trackers who install ports on their own only. Future -RELEASE users installing packages will see a working racoon. The new constants appear more sensible to me as they are in line with RFC 2407. Please keep it like it is; it's fairly easy to make a workaround. I would suggest to just document the necessity to re-build userland ISAKMP daemons in UPDATING instead. Regards, Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301312207.h0VM7Ih6030847>