Nigel Jones

Similar here, This time with a fedora beta 39 guest. Using applie virtualization I get these memory corruption failures (and then other i/o failure). Fedora (albeit 38) is running fine...

Here's example:

We've seen the same with egeria (link above) which affects both 2.3.4 and 2.3.5 of spring boot. 2.3.3 is working fine. We do have a dependency (maven build) on reflections...

Very much agree that if we are not becoming the owner/authoritative source for these test vectors, then simply using them as part of CI (as is the case with many...

My understanding is that with our current pqca structure we could raise the request for funding of ARM runners at the PQCA TAC, then potentially they could raise a request...

@ryjones thanks for requesting access again. I had assumed there will still be fees for using the arm runners once public. Maybe that concern is misplaced and some usage will...

My interpretation of the sequence leading up to the CI failure (github): (cc: @ryjones ) The test that fails is triggered by https://github.com/open-quantum-safe/liboqs/blob/a5ec23cf19763d36a558b8358345823ae45d57e5/.github/workflows/release-test.yml#L15 (well, in main). this then seems to...

I note they say their own routines use this feature too. Looks very useful, though we need to strive for all implementations being constant-time in any case. But I guess...

I'd agree with @baentsch that if the target is github markdown then using the github-supported configuration makes sense. I use markdownlint (defaults, in vscode) myself as a first-pass checker.

From a developer perspective, using :latest is very appealing for the reasons described above. In isolation it's what I'd prefer....! However in general one of the best practices of establishing...