New commits:
commit ec348d044c2a77ed03418b1f68a6d244ea5fbafb
Author: Andrew Cagney <[email protected]>
Date: Wed Mar 23 10:23:21 2022 -0400
testing: in interop-ikev2-strongswan-38-digsig-impair expect CERTREQ and
strong initiator
- since the responder (pluto) wants a signature it sends a certreq
- since the responder (pluto) doesn't see the initiator (strongswan)
SIGNATURE_HASH_ALGORITHMS notification, it proves its identity
using legacy rsa-sha1
however:
- since the initiator (strongswan) sees the responder (pluto)
SIGNATURE_HASH_ALGORITHMS it proves its own identity using
strong ECDSA
commit ef5463c930db31e8ed686c7bee77f69a5ca0e9ff
Author: Andrew Cagney <[email protected]>
Date: Wed Mar 23 10:21:25 2022 -0400
testing: in interop-ikev2-strongswan-38-digsig-impair expect CERTREQ
Since pluto is using ECDSA, expect a CERTREQ.
_______________________________________________
Swan-commit mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-commit
