From owner-freebsd-arch@FreeBSD.ORG  Thu Feb  5 00:46:04 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 304BB16A4CE
	for <arch@freebsd.org>; Thu,  5 Feb 2004 00:46:04 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8864343D31
	for <arch@freebsd.org>; Thu,  5 Feb 2004 00:46:02 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i158k0DF039613;
	Thu, 5 Feb 2004 09:46:00 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Doug White <dwhite@gumbysoft.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 04 Feb 2004 16:07:06 PST."
             <20040204160446.F96240@carver.gumbysoft.com> 
Date: Thu, 05 Feb 2004 09:46:00 +0100
Message-ID: <39612.1075970760@critter.freebsd.dk>
cc: arch@freebsd.org
Subject: Re: Resolving the crypto duplicity... 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2004 08:46:04 -0000

In message <20040204160446.F96240@carver.gumbysoft.com>, Doug White writes:
>On Wed, 4 Feb 2004, Poul-Henning Kamp wrote:
>
>>
>> I'm just using Rijndael/AES for illustration, the same issues apply
>> to various other algorithms.
>>
>> Right now we have identical (apart from some trivial details) of the
>> AES algorithms in the kernel:
>>
>> [1]	src/sys/crypto/rijndael/*
>> 	[ipsec, random and geom_bde options]
>>
>> [2]	arc/sys/opencrypto/rijndael.?
>> 	[crypto]
>
>You'd have to go back to the original discussion, but I though that we
>decided to go with this to avoid complicating KAME imports.
>
>Just trying to inject some history into the discussion :)

I realize that, but for something as generic as specific cryptographic
algorithms, I do not think that is a valid argument for having two
implementations in the kernel, particularly not for a case like the
AES implementation which is line-for-line identical.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.