I just happened to be working with this recently. It appears a common framework for software and hardware crypto support is avaialble through cryptoAPI. A crypto alg is abstracted through 'struct crypto_alg' and registered with 'crypto_register_alg()'. The module fills in the associated functions (encr/decr/ecb/cbc) and things like block size, key size, .. To make use (for example from IPsec setfkey) you can specify the alg name or driver name, for example "aes" will choose the first 'aes' alg found or "aes-padlock" will find the specific driver. IPsec Security Association will reference that cyrpto_algo for transmit/receive. This holds for digest as well as cipher algs. The 2.6.22.9 kernel appears to have couple hardware modules under drivers/crypto. - Mario -----Original Message----- From: lf_carrier-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx [mailto:lf_carrier-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Dan Kohn Sent: Thursday, November 15, 2007 11:30 AM To: lf_carrier@xxxxxxxxxxxxxxxxxxxx Cc: Jonathan Corbet Subject: Fwd: Request for review of SCOPE gaps document Jonathan Corbet, the editor of LWN <http://lwn.net/> and the Linux Weather Forecast <http://www.linux-foundation.org/lwf>, generously gave the SCOPE gaps document a quick review, attached below. He can't make the call today, but hopefully will be able to participate on the next CGL call. - dan -- Dan Kohn <mailto:dan@xxxxxxxxxxx> COO, The Linux Foundation <http://www.linux-foundation.org> <http://www.dankohn.com/> <tel:+1-415-233-1000> Unified crypto framework: I don't know as much about this as I would like to. The key management infrastructure in the kernel now should be part of what they want. There's also quite a bit of crypto capability in the kernel, including some hardware acceleration support. I'm not sure what has been done to export those capabilities to user space, though. _______________________________________________ Lf_carrier mailing list Lf_carrier@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/lf_carrier