New commits: commit d15ee6a7a969a352b76380b9c0a568652aff7070 Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:42:28 2014 -0400
testing: deleted ah-pluto-12 test commit 999eb2cf6113e9ca9c702baaa7c060c2f54ccad8 Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:41:31 2014 -0400 testing: ah-pluto-10 changed mismatching algos for additional test commit 983eea199728b0633a9e184aa597fb67f893e734 Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:40:57 2014 -0400 testing: repurposed ah-pluto-06 commit 8c708fd3b73de237c107d5a2404d5d17e49cb237 Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:40:15 2014 -0400 testing: updated ah-pluto-01/description.txt commit ac0c66d60102982ec2e9cb1a1277187fb1d3ed0c Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:39:29 2014 -0400 pluto: handle AES_CTR_SALT_BYTES commit 15b991fd3d6de186ba01121a2bd40424fc139932 Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:36:49 2014 -0400 alg_info: tidy commit 2d4534722dbabf0eda7ee678f41771443a938654 Author: Paul Wouters <pwout...@redhat.com> Date: Wed Oct 8 00:33:32 2014 -0400 kernel_alg: override AES_CTR registration key size from PFKEY answer The PFKEY answer includes the 4 bytes of salt, but we add those later on and use these values to determine actual key size, not keymat sizes. This caused aes_ctr128 to be rejected (as kernel states minimum 'keysize' is 169 (128+32) commit 8879a4a3ffdc9ff586de7a840cf4eaf960dc8653 Author: Paul Wouters <pwout...@redhat.com> Date: Mon Oct 6 16:18:13 2014 -0400 ikev2: enforce mandatory KEY_LENGTH on receiving responder child proposal _______________________________________________ Swan-commit mailing list Swan-commit@lists.libreswan.org https://lists.libreswan.org/mailman/listinfo/swan-commit