Mike Boquard

Force push [`2f935ca`](https://github.com/scylladb/seastar/compare/1a533615610fac2ae8fa02b2b5265f8926427188..2f935cac22094152c1ed51daf6d3edcbea087fad): * Addressed issues from comments * Created GnuTLS & OpenSSL implementations for SHA1-Base64 used by websocket * Fixed nits

Force push [db318da](https://github.com/scylladb/seastar/commit/db318daadfd31fadb14c45c8f128c1820a0a1a02): * Addressed PR comments

Force push [245d15c](https://github.com/scylladb/seastar/commit/245d15c8239a7db7f48c23e47dfe88171c716611): * Rebased off master to fix merge conflicts introduced by https://github.com/scylladb/seastar/commit/6f39b89dbda812c7985918d3d8d6d7f7792b0619#diff-2f6778574276aef7b957daacf9904fc252fe1b44d45819bc89daafce9dac3972R1042

Force push [cab469f](https://github.com/scylladb/seastar/commit/cab469f91be311fec34400502796a3eefe4c282c): * Fixed typo

Force push [47dfb11](https://github.com/scylladb/seastar/commit/47dfb11081910d5e70c02498d031633f66b1d1ec): * Fixed logic of `get_security_level` * Returning anything >1 when using OpenSSL 3.0 will introduce key restrictions that may cause Seastar to be unable to connect with...

> Note test failures It appears all failures are from `Seastar.unit.rpc`, which I don't believe interacts with the TLS. Were they flaky before? > Can we translate the priority string...

> Can we translate the priority string to openssl config? I asked Claude and it spewed a long python script, maybe that's good enough. I guess your question is "can...

> Is there no equivalent textual configuration? AFAIK only through the OpenSSL config file which can be loaded either automatically by OpenSSL when it is initialized or can be controlled...

Hi again @avikivity and @elcallio . Apologies for such a long delay in updating this PR. I've made some updates and rebased off of master.

Hi again @avikivity and @elcallio . Was wondering if there was anything I could do to assist in regards to this PR?