Date: Sat, 09 Aug 2008 11:08:22 -0700 From: Sam Leffler <sam@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, Philip Paeps <philip@freebsd.org> Subject: Re: cvs commit: src/sys/conf files.i386 src/sys/dev/glxsb glxsb.c glxsb.h glxsb_hash.c src/sys/i386/conf NOTES src/sys/modules Makefile src/sys/modules/glxsb Makefile Message-ID: <489DDD16.7000907@freebsd.org> In-Reply-To: <97980.1218298242@critter.freebsd.dk> References: <97980.1218298242@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote:
> In message <200808091453.m79ErIuP092318@repoman.freebsd.org>, Philip Paeps writ
> es:
>
>> philip 2008-08-09 14:52:31 UTC
>>
>>
>
>
>> Add glxsb(4) driver for the Security Block in AMD Geode LX processors (as
>> found in Soekris hardware, for instance). The hardware supports acceleration
>> of AES-128-CBC accessible through crypto(4) and supplies entropy to random(4).
>>
>> TODO:
>>
>> o Implement rndtest(4) support
>>
>
> Just for the record: I think it is important that we have a test-program
> that checks that these hardware assisted crypto algorithms actually
> do the right thing.
>
> I would really hate if people found out that they had been using
> the ROT52 algorithm due to some silly bug we don't notice along the
> way.
>
> It doesn't have to be very advanced, just run a couple of the standard
> test-vectors to see that the result is correct.
>
>
tools/tools/crypto/cryptotest is kinda setup to do that. No test
vectors though.
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?489DDD16.7000907>