From owner-cvs-src@FreeBSD.ORG Sat Aug 9 16:10:44 2008 Return-Path: Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4BF9106568D; Sat, 9 Aug 2008 16:10:44 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 9028C8FC12; Sat, 9 Aug 2008 16:10:44 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 616E4170E4; Sat, 9 Aug 2008 16:10:43 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m79GAgAF097981; Sat, 9 Aug 2008 16:10:43 GMT (envelope-from phk@critter.freebsd.dk) To: Philip Paeps From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 09 Aug 2008 14:52:31 GMT." <200808091453.m79ErIuP092318@repoman.freebsd.org> Date: Sat, 09 Aug 2008 16:10:42 +0000 Message-ID: <97980.1218298242@critter.freebsd.dk> Sender: phk@critter.freebsd.dk 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 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Aug 2008 16:10:45 -0000 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.