From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 9 21:16:20 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78FE91065695; Thu, 9 Oct 2008 21:16:20 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (smtp.zeninc.net [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 34DA38FC29; Thu, 9 Oct 2008 21:16:20 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from albator.zen.inc (albator.zen.inc [192.168.1.5]) by smtp.zeninc.net (smtpd) with ESMTP id 232B1279899; Thu, 9 Oct 2008 22:56:37 +0200 (CEST) Received: by albator.zen.inc (Postfix, from userid 1000) id 82770731D6; Thu, 9 Oct 2008 22:56:36 +0200 (CEST) Date: Thu, 9 Oct 2008 22:56:36 +0200 From: VANHULLEBUS Yvan To: alan yang Message-ID: <20081009205636.GA3002@zeninc.net> References: <290865fd0810090846y57bbdc1fs3db5c5334fe80c09@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <290865fd0810090846y57bbdc1fs3db5c5334fe80c09@mail.gmail.com> User-Agent: All mail clients suck. This one just sucks less. Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: setkey panic freebsd7 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2008 21:16:20 -0000 Hi. On Thu, Oct 09, 2008 at 08:46:32AM -0700, alan yang wrote: > i wonder people ran into similar issue on setkey with freebsd7 that > panic at ~/crypto/sha1.c:263 within sha1_result() > digest[0] = ctxt->h.b8[3]; digest[1] = ctxt->h.b8[2]; > > on the following sadb add with setkey: > add 192.168.0.101 192.168.0.110 esp-old 0x10001 -m any -E des-cbc > "12345678" -A keyed-sha1 "12345678123456781234" > > thanks in advance on any hints. I guess most people just don't use static SAs anymore :-) Can you reproduce the bug ? Are you using /sbin/setkey (provided by FreeBSD), /usr/local/sbin/setkey (provided by ipsec-tools), or does it crash with both ? If you can reproduce it, please fill in a PR, Bjoern or I will take it. Anyways, I'll have a look asap at that part of the code, to see if I can find "something". Any extra information on how to reproduce the bug is welcome ! :-) Yvan.