I looked into this and was tempted as there is less read locking and better RNG performance but they stripped the SSL_get1_curves() API which I depend on for bot detection plus I would have to recompile nginx and all its modules everywhere so in the end it was not tempting enough for me. Perhaps I am just lazier in my older age.
We ran a number of tests, including sending a percentage of real traffic to endpoints running AWS-LC and Wolfssl. Technically yes, OpenSSL 3.X is slow, measurably so, but not enough that we wanted to deal with it. That's for our use case, I can easily imagine there being others, where maybe you have different hardware or way more traffic, where it would be worth while. For basic TLS termination in haproxy, it wasn't really worth it to us.
It also depends on exactly which version of OpenSSL. We ran similar tests with multiple versions of openssl. Openssl 3.0, which was the version in the official packages of our LTS distro was unacceptably slow. With 3.4, it was still worse than 1.1.1 but the regression was an acceptable level.
It also definitely depends on your hardware, and how you use it. The main source of the performance regression is more lock contention, so it is more noticeable if you have more threads running on more cores.
I think all of this dead end: it is like protecting your apartment only by strong locks etc. Modern society protects from crime using punishment and moral norms. Not only by locks.
How would this work without having to totally prevent anonymity on the internet? As long as you can log in from a country that doesn’t care about cybercrime, how would you prevent people from hacking others? You’ll never punish a North Korean hacker
I think in this case, it's the hackers that are supposed to be deanonymised and prosecuted. Deanonymization in general is hard, but while they still use the IP, it's not. ISP already do store the IP mapping for precisely this case.
> You’ll never punish a North Korean hacker
You don't need to, you can fine the whole country.
reply