Gerardo Ravago

With that serial parsing fix, here's the last CI failure that needs to be addressed. When run with `--enable-leak-detector` I've got these two memory leaks from internal `RAND_bytes` related state....

> so if something is freed only when that thread is terminated, leak detective will flag it. Yes, that's exactly what's happening here. RAND_bytes allocates some thread specific data and...

In PR #2151 you asked about adding a function to ID EC_KEY's from explicit curves. It turns out BoringSSL and AWS-LC don't support explicit curves at all. Here's a [comment](https://github.com/openssl/openssl/issues/9286#issuecomment-561777868)...

If there's anything you'd like to change in the unit tests or plugin regarding this explicit EC parameter behavior let me know and I can put that together. Otherwise, I...

Resolving as stale and underspecified. While I agree that adding more telemetry is generally useful, we can open a new issue when we have crisper requirements around specific metrics, technical...

@csosto-pk, can we close this issue in favor of Issue #163? I plan on adding support for `mlkem768nistp256-sha256` and `mlkem1024nistp384-sha384` there. I also plan on looking into the implementation effort...

I'm picking this up to help get the project back in an up to date and healthy state. The current upstream OpenSSH version is 9.7 so I'll target that under...

Can a maintainer create an `OQS-v9` branch based at the current tip so that I can cut a PR to merge into it? I think it makes sense to maintain...

Can someone [disable](https://docs.github.com/en/actions/using-workflows/disabling-and-enabling-a-workflow) the upstream Github workflows on the v9 branch/repository? Historically, I see that only the Circle CI checks should be running (e.g. [last PR on v8](https://github.com/open-quantum-safe/openssh/pull/157)). My latest...

Thanks! Getting these to run seem to be long-running issue (Issues #89, #90). I took a peek and it looks like two things need to get done: 1 - build/setup...