Date: 24 Jun 2001 18:38:31 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: "Karsten W. Rohrbach" <karsten@rohrbach.de> Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Status of encryption hardware support in FreeBSD Message-ID: <xzpzoax6dfc.fsf@flood.ping.uio.no> In-Reply-To: <20010624183147.F52432@mail.webmonster.de> References: <3B33A891.EC712701@soekris.com> <xzpn16x7uao.fsf@flood.ping.uio.no> <20010624181007.C52432@mail.webmonster.de> <xzpd77t7st6.fsf@flood.ping.uio.no> <20010624183147.F52432@mail.webmonster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
"Karsten W. Rohrbach" <karsten@rohrbach.de> writes: > yup, exactly. to me it seems to be a major problem to get some unified > api out of openssl adressing fucnctions on the hardware -- i simply do > not know how other crypto chipsets do it, i just investigated the > rainbow board. they got a patch against openssl 0.9.5 i think, that > glues in the driver calls instead of standard lib functions. Can you dig out this patch for me? It would be a big win if the userland interface to Soren's hardware were compatible with Rainbow's driver. > yes yes yes ;-) you are perfectly right here. i just wanrted to mention > that there is an _existant_ driver and patch against the openssl lib, > also some test programs to look if the driver works, for freebsd 3.x. This would be useful for ensuring compatibility with Rainbow's stuff, especially if, as you say, they have a 4.1 version out now. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpzoax6dfc.fsf>