pinkforest(she/her)

I wired up comparison suite from OpenSSL to the point where it can be constrained to negotiate specific algorithms

I constrained the groups and cipher suites in #66 + autoneg testing

Does anyone remember know / what happened at IETF with OCB getting it to TLS 1.3 ? Like after [draft-zauner-tls-aes-ocb-04](https://datatracker.ietf.org/doc/draft-zauner-tls-aes-ocb/) Or https://mailarchive.ietf.org/arch/msg/tls/qZiGzQiePuURYTZrd3bHUFKrtD4/ I'm keen getting AEGIS supported given CAESAR entry...

When [doing #66](https://github.com/RustCrypto/rustls-rustcrypto/pull/66#issuecomment-2081370010) it reminded OpenSSL has Goldilocks / curve448 supported group - since 2018 and FIPS 186-5 / RFC8418

Frank has brought in Rust AEGIS here: https://github.com/jedisct1/rust-aegis Would love to compose these things universaly via cfg's coming together at the rustls using binary - so raised issue: - https://github.com/jedisct1/rust-aegis/issues/5...

We could maybe just plug into these at minimum: - https://github.com/rustls/rustls/tree/main/fuzz

So first release would be 0.23.0 ? - What happens if/when we have (we already have provider() constructor) our own API and we need to bump our API ? -...

The problem with this is, it pollutes the dependencies and as I said before it brings dependencies that may not be in lock-step on what rustls we are developing -...

Probably this: - https://github.com/phsym/prettytable-rs/blob/master/src/utils.rs#L86 Needs re-work - wanna do and send a patch that contains proper testing of it ?

Pinning dependencies asks for trouble e.g. duplication etc. It needs to be addressed here as compat issue if so. Someone just has to work on it and submit a patch.