Hi Holger,

> server requested EAP_AKA authentication (id 0x00)
> EAP method not supported, sending EAP_NAK

> loaded plugins: charon test-vectors aes rc2 sha1 sha2 md4 md5 random
>  nonce x509 revocation constraints pkcs1 pkcs7 pkcs8 pkcs12 pem open
>  ssl xcbc cmac hmac ctr ccm gcm attr kernel-netlink resolve
>  socket-default stroke updown eap-identity eap-aka eap-aka-3gpp2
>  addrblock

EAP-AKA not only needs a backend (such as eap-aka-3gpp2, which you have
loaded), but also a special PRF implemented in the fips-prf plugin.

That plugin should get enabled implicitly if you ./configure with
--enable-eap-aka, but you might need to update any manual
strongswan.conf load statements.

Regards
Martin

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Users mailing list
Users@lists.strongswan.org
https://lists.strongswan.org/mailman/listinfo/users

Reply via email to