From owner-freebsd-security@FreeBSD.ORG  Wed Oct 14 22:54:43 2009
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AF6DA106566B
	for <freebsd-security@freebsd.org>;
	Wed, 14 Oct 2009 22:54:43 +0000 (UTC)
	(envelope-from rwmaillists@googlemail.com)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26])
	by mx1.freebsd.org (Postfix) with ESMTP id 3F3F88FC0C
	for <freebsd-security@freebsd.org>;
	Wed, 14 Oct 2009 22:54:42 +0000 (UTC)
Received: by ey-out-2122.google.com with SMTP id 9so87797eyd.9
	for <freebsd-security@freebsd.org>;
	Wed, 14 Oct 2009 15:54:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:date:from:to:subject
	:message-id:in-reply-to:references:x-mailer:mime-version
	:content-type:content-transfer-encoding;
	bh=t4fdzXMwlbcImf7/dS+vsSSfDBJCOyJDjyxYeDHb8uk=;
	b=fjn2k9FhRByl69mtGP1GHDIG35ogKb/CggA1SGu5YqbkU/N09gxwaaeZR5YJqL9tpf
	zkGWY4tI+rKhel95i9Hf+/gZaYFrugvHxT48YsyLdMXPpI+srDjFA26GAHlNPH3tGq0R
	NmKq2tWSZc4hoBnMtJ9CmT6VoIgTk+nQDcA5s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=date:from:to:subject:message-id:in-reply-to:references:x-mailer
	:mime-version:content-type:content-transfer-encoding;
	b=jvI+p9s//vsA9F1MgXkQZk6GDGuEUHmarlDh64DNw9eKX/rmlBsf25n6Sn+EOO3ejP
	ap7G2zHepNOhYBPXbAFU1DOPXR514hd18btqfkYbGiSX7H40W38eh+iANS0GwgkSw8p7
	C3LsCHEQAywdhsyCXCu4sV4Uw+PAVYmq4Ebts=
Received: by 10.211.126.15 with SMTP id d15mr7926836ebn.19.1255558990877;
	Wed, 14 Oct 2009 15:23:10 -0700 (PDT)
Received: from gumby.homeunix.com (bb-87-81-140-128.ukonline.co.uk
	[87.81.140.128])
	by mx.google.com with ESMTPS id 7sm766441eyb.40.2009.10.14.15.23.09
	(version=SSLv3 cipher=RC4-MD5); Wed, 14 Oct 2009 15:23:10 -0700 (PDT)
Date: Wed, 14 Oct 2009 23:23:07 +0100
From: RW <rwmaillists@googlemail.com>
To: freebsd-security@freebsd.org
Message-ID: <20091014232307.4f6d8479@gumby.homeunix.com>
In-Reply-To: <Pine.NEB.4.64.0910141754330.12911@otaku.freeshell.org>
References: <Pine.NEB.4.64.0910141754330.12911@otaku.freeshell.org>
X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: FreeBSD equivalent to Sun crypto framework APIs (PKCS#11) (for
 hardware AES-CTR)
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2009 22:54:43 -0000

On Wed, 14 Oct 2009 18:02:36 +0000 (UTC)
John Case <case@sdf.lonestar.org> wrote:

> 
> There are a number of hardware solutions for performing AES-CTR in 
> hardware - for example the broadcom BCM5825, which is supported by
> the ubsec driver.
> 
> The problem is that OpenSSL does not currently support hardware 
> acceleration of AES-CTR.  The solution on a Sun system is to use the
> Sun crypto framework APIs (PKCS#11) which does support AES-CTR in
> hardware.
> 
> Is there an analagous API in FreeBSD that I could implement in my
> code so as to use the hardware AES-CTR of devices supported by ubsec ?

Aside from  crypto(3) (OpenSSL), there's also crypto(9) (kernel) and
crypto(4) (userland), but they don't appear to support CTR - just CBC.