[Openswan dev] Re: [Openswan Users] Hardware encryption support - VIA PadLock?

[Nate Carlson]

On Mon, 21 Jun 2004, Nate Carlson wrote:
> If anyone has any ideas (or if I'm going about things in the wrong way),
> I'd appreciate it!

OK, did a bit more hacking.

I've attached a patch that seems to get CryptoAPI working:

lips_info:ipsec_init: KLIPS startup, Openswan KLIPS IPsec stack version: 2.2.0dr1
klips_info:ipsec_alg_init: KLIPS alg v=0.8.1-0 (EALG_MAX=255, AALG_MAX=251)
klips_info:ipsec_alg_init: calling ipsec_alg_static_init()
setup_ipsec_alg_capi_cipher(): alg_type=15 alg_id=12 name=aes keyminbits=128 keymaxbits=256, ret=0
setup_ipsec_alg_capi_cipher(): alg_type=15 alg_id=253 name=twofish keyminbits=128 keymaxbits=256, ret=0
setup_ipsec_alg_capi_cipher(): alg_type=15 alg_id=252 name=serpent keyminbits=128 keymaxbits=256, ret=0
setup_ipsec_alg_capi_cipher(): alg_type=15 alg_id=6 name=cast5 keyminbits=128 keymaxbits=128, ret=0
setup_ipsec_alg_capi_cipher(): alg_type=15 alg_id=7 name=blowfish keyminbits=96 keymaxbits=448, ret=0

It breaks the built in AES support, though. Certainly shouldn't be
commited to the source tree; just works for me (tm).

------------------------------------------------------------------------
| nate carlson | natecars at natecarlson.com | http://www.natecarlson.com |
|       depriving some poor village of its idiot since 1981            |
------------------------------------------------------------------------