On Fri, 2 Mar 2012, satpal parmar wrote:
I recently ported Openswan on ARM cortex based SOC running linux 2.6.37 (ipsec netkey stack) and openswan 2.6.23. On this board I have H/W accelerator support for AES/DES/SHA. (http://processors.wiki.ti.com/index.php/Installing_AM387x_C6A814x_DM814x_Crypto_Support). AES/DES crypto operation are working fine and I am able to ping through IPsec tunnel from my board to PC and vice versa.
Did you need to patch anything for openswan? Can you share your patches with us?
However when I am trying ping with SHA-MD5 I am not able to ping to and from Ubuntu machine .
My ubuntu machine details: root@vnl-desktop:~# uname -a Linux vnl-desktop 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:08:37 UTC 2011 i686 GNU/Linux MYost probably it could be a IPsec configuration issue on Ubuntu machine but I am not able to locate what configuration could affect behavior of only one crypto algorithm. Since I am using same configuration for IPsec for testing all Crypto algo supported in H/W (DES/AES/SHA-MD5 )and I am successfully able to ping through IPSec tunnel for DES and AES.
I am not sure what you mean when you bundle "sha-md5" and "des and aes". A tunnel needs both an encryption algorithm (aes or 3des) and an authentication algothim (sha1, sha2, md5, etc). So for your tunnel to work, you would always be using either md5 or sha? Since you say some tunnels work, those algorithms must be working? I am not sure I understand exacly what works and what does not work. Paul -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
