Steffen Jaeckel

Can you provide debug logs? We can also discuss this in the profanity MUC.

> `2023-04-04T10:44:53.148139+03: tls: DBG: error=SSL_ERROR_SYSCALL(5) errno=104 lasterror=0` errno 104 is as of [errno.h:87](https://github.com/torvalds/linux/blob/148341f0a2f53b5e8808d093333d85170586a15d/include/uapi/asm-generic/errno.h#L87) ```c #define ECONNRESET 104 /* Connection reset by peer */ ``` i.e. the connection was closed by...

> Not sure what to do against this. escape the char?

> At which point? yes :laughing: It's a CLI, so it should behave like the CLI's we're all used to, i.e.: * when user creates input to the CLI, this...

Well I guess that's part of the 'Missing something?' ... Maybe this will also lead to different usage behavior!? ... This needs to be thoroughly thought through and checked, but...

Did you try the proposed change of #641 and whether this maybe fixes it already?

Sorry for the long delay. > #641 doesn't help, unfortunately. Here is a crash from the `fix-perl-cryptx-99` branch on a machine without SSE4.1 (running OpenBSD): > > ``` > $...

And also you're right with this PR... now I understand the purpose :) With this we have now a "proper" runtime check for AES-NI. It allows to build the rest...

This also supersedes #641 right?

Before merging this I have one more question: Wouldn't it now make sense to enable this by default on x86/amd64? If yes, we should change the compile-time-switch to disable if...