Reviewed: https://review.openstack.org/306683 Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=b16bc6cffa31fd97330f462429f31d90093886c6 Submitter: Jenkins Branch: master
commit b16bc6cffa31fd97330f462429f31d90093886c6 Author: nick.zhuyj <[email protected]> Date: Fri Apr 15 23:18:31 2016 -0500 Support sha256 for vpn-ikepolicy and vpn-ipsecpolicy Currently only sha1 is supported for vpn ikepolicy and ipsecpolicy config. One patch is already merged to support sha256 for these 2 configs. Sync neutron command to support sha256. Change-Id: I8c1189bd0eba3de12cd1ef78b795e46efe65c29e Depends-On: I02c80ec3494eb0edef2fdaa5d21ca0c3bbcacac2 Closes-Bug: #1567846 ** Changed in: python-neutronclient Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1567846 Title: VPNaaS: require to support sha256 Status in neutron: Fix Released Status in python-neutronclient: Fix Released Bug description: Currently, only sha1 is supported in auth-algorithm. But there is requirements to support sha256. In current implementation, strongswan ipsec.conf.template doesn't include ike & esp filed, so by default. sha256 is used. In this bug, we only talking about openswan. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1567846/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
