Encode EAP-Naks in expanded format if we got an expanded type request
authorTobias Brunner <tobias@strongswan.org>
Thu, 23 Aug 2012 06:36:24 +0000 (08:36 +0200)
committerTobias Brunner <tobias@strongswan.org>
Fri, 31 Aug 2012 09:40:27 +0000 (11:40 +0200)
commitcc4eec56f73ef54386badc8732b1867cbe05b47f
treed23b3134094aecb96deeedec32b30bd28b0d19e1
parent78e8dca94f86b97b7df649c1c96a7fe532019a5f
Encode EAP-Naks in expanded format if we got an expanded type request

Since methods defined by the IETF (vendor ID 0) could also be encoded in
expanded type format the previous check was insufficient.
src/libcharon/encoding/payloads/eap_payload.c
src/libcharon/encoding/payloads/eap_payload.h
src/libcharon/plugins/eap_peap/eap_peap_peer.c
src/libcharon/plugins/eap_ttls/eap_ttls_peer.c
src/libcharon/sa/ikev2/authenticators/eap_authenticator.c