Hi, > on systems lacking AES-NI support critical strongswan processes (charon, > swanctl) get terminated by SIGILL in libstrongswan-aesni.so.
The plugin definitely checks for AES-NI and PCLMULQDQ at runtime. But what it did not do so far is check for SSSE3 (the next release will do so). So are you running on a CPU that has AES-NI and PCLMULQDQ instructions but lacks support for SSSE3? Maybe virtualized? > The issue is that strongswan applications auto-load all plugins and > libstrongswan-aesni.so loads even when AES-NI are not available. It's loaded but it doesn't register any plugin features if the required CPU features are not found. So it shouldn't cause any SIGILL when running on unsuitable hardware (except in the combination mentioned above). Regards, Tobias
