> Isn't it the way it works when wpa_supplicant's tnc client loads any imc > (.so) so everything runs in the same process space?
When using strongSwan imc/imv modules from wpa_supplicant, this of course is a different thing. You'll then have a single process, and OpenSSL initialization becomes an issue. As libimcv uses a hardcoded plugin list, probably it was never considered to be used with the openssl plugin. Your patch is certainly an option here, but it doesn't resolve the libcrypto initialization conflict. Maybe there is a way to detect if OpenSSL has already been initialized? Regards Martin _______________________________________________ Dev mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/dev
