Control: tags -1 bookworm Hello,
> > Result from gdb: Illegal instruction is punpcklqdq in aesni_plugin_create. > > <+60>: punpckldq %xmm2,%xmm1 > > <+64>: punpckldq %xmm3,%#mm0 > > =><+68>: puncpklqdq %xmm1,%#mm0 > > <+72>: movups %xmm0,(%eax) > > <+75>: add $0x18,%esp > > Oh, interesting. The complete `aesni` plugin is compiled with `-maes > -mpclmul -mssse3`. That apparently causes the compiler to "optimize" > the code there. I guess we could split the plugin into a helper library > that uses those flags and compile the plugin constructor/detection code > without it. I've pushed such a change to the devel branch [1]. Nice to see strongswan design makes this easy. Though it's more like "implementation" library than "helper". > Anyway, another question is if it actually makes sense to ship the > plugin in Debian. The default crypto library is OpenSSL nowadays and > since that will use AES-NI etc. anyway (likely more optimized than this > plugin), there is probably not much use having `aesni` enabled as well. Good question, especially for i386. Best, n.b.f. [1] https://github.com/strongswan/strongswan/commit/553ac5678b50729da896fa07ff8bc502a2a8f3da
