Date: Sat, 09 Aug 2008 16:10:42 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Philip Paeps <philip@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@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: <97980.1218298242@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 09 Aug 2008 14:52:31 GMT." <200808091453.m79ErIuP092318@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97980.1218298242>