strongswan builds without support for the different EAP modules. My idea is to add the "eap" use-flag, and make it enable the following modules in the configure script: --enable-eap-sim enable SIM authenication module for EAP. --enable-eap-sim-file enable EAP-SIM backend based on a triplet file. --enable-eap-simaka-sql enable EAP-SIM/AKA backend based on a triplet/quintuplet SQL database. --enable-eap-simaka-pseudonym enable EAP-SIM/AKA pseudonym storage plugin. --enable-eap-simaka-reauth enable EAP-SIM/AKA reauthentication data storage plugin. --enable-eap-identity enable EAP module providing EAP-Identity helper. --enable-eap-md5 enable EAP MD5 (CHAP) authenication module. --enable-eap-gtc enable PAM based EAP GTC authenication module. --enable-eap-aka enable EAP AKA authentication module. --enable-eap-aka-3gpp2 enable EAP AKA backend implementing 3GPP2 algorithms in software. Requires libgmp. --enable-eap-mschapv2 enable EAP MS-CHAPv2 authenication module. --enable-eap-radius enable RADIUS proxy authenication module. Let me know if it's okay for me to add this to the ebuild myself :) Reproducible: Always Steps to Reproduce: Actual Results: strongswan is built without the EAP modules Expected Results: strongswan should be built with the EAP modules
@Bjarke: Why don't you assign the bug properly yourself next time?
@Bjarke: Sorry got the message about this bug just now. I'll have to read up on the eap stuff. Once I've done that we can discuss if a simple eap useflag is enough or if there should be more to it. I hope that's okay with you. Please, don't get me wrong: I could have simply said "yes go ahead" but I like to know first what I am agreeing to or talking about respectively. :-)
Created attachment 251347 [details] Modified ebuild Sure - I have attached my modified ebuild - it just adds the configure parts, the normal install stuff installs all the modules already, so that works with these too. I'm currently using it myself without any problems.
Fixed with the 4.5.0 version in the tree.
