From owner-freebsd-security@FreeBSD.ORG Fri Jan 14 15:21:59 2005 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB3A316A4CE for ; Fri, 14 Jan 2005 15:21:59 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E77A43D2D for ; Fri, 14 Jan 2005 15:21:59 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 81661652FE; Fri, 14 Jan 2005 15:21:57 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 36227-02-2; Fri, 14 Jan 2005 15:21:57 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 699AB65218; Fri, 14 Jan 2005 15:21:56 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id AC7336132; Fri, 14 Jan 2005 15:22:22 +0000 (GMT) Date: Fri, 14 Jan 2005 15:22:22 +0000 From: Bruce M Simpson To: Andriy Gapon Message-ID: <20050114152222.GG57985@empiric.icir.org> Mail-Followup-To: Andriy Gapon , freebsd-security@freebsd.org References: <41E796DC.2090102@icyb.net.ua> <20050114140709.GD57985@empiric.icir.org> <41E7DAC3.3050707@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E7DAC3.3050707@icyb.net.ua> cc: freebsd-security@freebsd.org Subject: Re: debugging encrypted part of isakmp X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 15:21:59 -0000 On Fri, Jan 14, 2005 at 04:44:19PM +0200, Andriy Gapon wrote: > So, I am looking for the easiest way to decrypt isakmp packets using > both packet data and information like pre-shared keys, certificates etc. There's probably not a lot that you can do here, short of turning on all the debugging switches you can find for the opaque IKE implementation you're dealing with; unless the isakmp decoder in tcpdump were modified to accept keying material. We already do this for AH, ESP, TCP-MD5 but not IKE itself as that's a non-trivial task. Regards, BMS