Date: Thu, 10 Jul 2008 07:46:18 -0400 From: Mike Tancsa <mike@sentex.net> To: Patrick =?iso-8859-1?Q?Lamaizi=E8re?= <patfbsd@davenulle.org> Cc: freebsd-stable@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) Message-ID: <200807101146.m6ABkJib035927@lava.sentex.ca> In-Reply-To: <20080710130904.6c06fdfb@baby-jane-lamaiziere-net.local> References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> <200807091931.m69JVWej032290@lava.sentex.ca> <20080710130904.6c06fdfb@baby-jane-lamaiziere-net.local>
next in thread | previous in thread | raw e-mail | index | archive | help
At 07:09 AM 7/10/2008, Patrick Lamaizi=E8re wrote:
>I've found, i think. The Geode handles only AES with a 128 bits key.
>
>When setkey/ipsec opens a crypto session, the driver returns an error
>(EINVAL) if the key length is !=3D 128. So setkey fails.
>
>There is no way to tell to the crypto framework that we can do only AES
>with 128 bits keys. It is a problem in this case.
Hi,
Yes, that appears to be it!
>I don't have any solution, I can just add a BUG section in the man
>page for this case.
Perhaps just a limitation/caveat as opposed to a=20
bug :) Thanks for porting this over! I will=20
give it a try with openvpn next. Any plans to integrate it into the tree ?
---Mike=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807101146.m6ABkJib035927>