From owner-freebsd-bugs@FreeBSD.ORG Tue Nov 11 13:30:16 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1555B16A4CE for ; Tue, 11 Nov 2003 13:30:16 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8753F43FEA for ; Tue, 11 Nov 2003 13:30:15 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hABLUFFY048903 for ; Tue, 11 Nov 2003 13:30:15 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id hABLUFse048902; Tue, 11 Nov 2003 13:30:15 -0800 (PST) (envelope-from gnats) Date: Tue, 11 Nov 2003 13:30:15 -0800 (PST) Message-Id: <200311112130.hABLUFse048902@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mark Linimon Subject: Re: kern/58899: [fix] ipfw2 ipsec history option not working X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mark Linimon List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 21:30:16 -0000 The following reply was made to PR kern/58899; it has been noted by GNATS. From: Mark Linimon To: freebsd-gnats-submit@FreeBSD.org, bzeeb+freebsd@zabbadoz.net Cc: Subject: Re: kern/58899: [fix] ipfw2 ipsec history option not working Date: Tue, 11 Nov 2003 06:53:52 +0000 Adding to audit log from misfiled PR 58910: Ari Suutari wrote: Wow ! The initial patch I submitted must have been incomplete somehow, because I really tested this thing on -current. The reason might be that the first patch didn't include #ifdef IPSEC at all. Then someone (maybe me on another machine...) who tested it complained about kernel not compiling without IPSEC - and I added the #ifdef IPSEC without testing it 'since it was such a small change'. Please someone, commit the suggested patch. Also, if these changes have gone to 4.9, it might be good to include this fix for RELENG_4_9 since it is security related. Ari S. [guess it's too late for that last part -- mcl]