From owner-freebsd-security@FreeBSD.ORG  Thu Apr  8 07:28:40 2004
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 DC67816A4CE
	for <security@freebsd.org>; Thu,  8 Apr 2004 07:28:40 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4BB2143D2D
	for <security@freebsd.org>; Thu,  8 Apr 2004 07:28:40 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i38ESbAZ026216;
	Thu, 8 Apr 2004 16:28:37 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Mike Tancsa <mike@sentex.net>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 08 Apr 2004 10:25:59 EDT."
             <6.0.3.0.0.20040408102521.0948ea58@209.112.4.2> 
Date: Thu, 08 Apr 2004 16:28:37 +0200
Message-ID: <26215.1081434517@critter.freebsd.dk>
cc: security@freebsd.org
Subject: Re: recommended SSL-friendly crypto accelerator 
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2004 14:28:41 -0000

In message <6.0.3.0.0.20040408102521.0948ea58@209.112.4.2>, Mike Tancsa writes:
>At 10:14 AM 08/04/2004, Poul-Henning Kamp wrote:
>
>>Look at VPN14x1 from www.soekris.com, it's darn cheap too.
>
>The driver is broken in both RELENG_4 and CURRENT however.

It is not clear to me exactly what is broken.  I have seen problems
reported but as far as I know they were all IPSEC related, and I
have not seen a trace of trouble in my use with GBDE.

I'm not saying that the driver is _not_ broken, but it is certainly
not known to me to be broken for the use Michael asked about.

-- 
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.