Spencer Wilson

I would welcome the addition of an algorithm in which there is clear community interest and for which we have a committed maintainer—let's do it. I would only add the...

In case it helps anyone working on this in the future, I got started on this in this branch: https://github.com/open-quantum-safe/liboqs/compare/sw-alg-datasheet.

> We get three users. > > Who should I turn off? I'm fine with not having access.

> OK. > > What builds do we get out of Travis? I would prefer to concentrate usage onto platforms we already pay for (GitHub, EC2) We use Travis for...

Regardless of platform support commitments, I do like having tests that run on non–little-endian systems, if only to ensure that any patches we introduce don't break the property of an...

> If using IBM HW (as a big endian test env) in GH were possible that'd be great and allow us to get rid of the more unreliable Travis stuff:...

Hey @bhess—just wanted to check if this was still on your radar. If you don't have bandwidth right now, maybe @ryjones can get the process started.

As per in-person discussion with @dstebila and @praveksharma, Douglas will ask colleagues from AWS about the future of BIKE at conference(s) this month. If it is to be deprecated, it...

We will not be making a deprecation announcement for BIKE in the upcoming 0.13.0 release. We'll revisit this in a future release cycle.

Hi, @psheer-spirent. I do agree that [Appendix A of FIPS 205](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.205.pdf#appendix.A) makes it sound like SLH-DSA and SPHINCS+ 3.1 should be the same on the parameter sets we support. However,...