Spencer Wilson

> I managed to reproduce this very rare verification error in CROSS-RDSDP-128-small. I'm still looking for the root cause but I can confirm that it seems totaly unrelated to the...

Thanks for the contribution @nathaniel-brough!

I don't know what format IAIK is using for ML-DSA keys—if they're storing private keys as "seeds" then oqs-provider won't know how to handle them. However, it looks like you...

I could be wrong, but I believe that https://datatracker.ietf.org/doc/html/draft-ietf-lamps-dilithium-certificates-07 (and all previous versions) specify that the private key should be stored as an ASN.1 OCTET STRING. Have you checked with...

> Looks like stalled last year. I could maybe pick it up if I get some time from my company, but I'd need some direction. Hi @knightcode, we do have...

> @SWilson4 would it be sensible then to assign this issue to this person so everyone immediately sees this issue as being worked on? Good call---I tried just now, but...

> Second thought: Would this have to be part of `oqsprovider` setup at all? The way I read the discussion it seems to be more sensible to make this a...

> > How about we discuss the best way to bring this into the provider (if at all) over there? > > Good with me. But I'm not seeing any...

Hi @RodriM11, thanks for the feature request! Could you expand a little on your use case for derandomized encapsulation? The main motivations for adding derandomized key generation for ML-KEM to...

> Hi [@SWilson4](https://github.com/SWilson4) , thanks for the quick response. IMO, for example similar uses would be desirable under the inclusion of this feature: > > * deterministic testing of Encaps...