Closed t8m closed 1 month ago
@baentsch Could you please look into this?
@t8m , sure. Problem is that the external CF server changed its behaviour at that port (not running x25519-kyber any more but x25519-mlkem). This will be automatically corrected once the next oqsprovider release comes along doing the same change. But that's 1-3 weeks away as the OQS colleague implementing that is at ICMC...
Is that sufficient or should we do something to fix this faster? The only short-term thing I can think of is removing the test, i.e. either the whole oqsprovider test or a patch within openssl to facilitate that for now (need to check how). Any preference on your side?
I've merged the urgent CI fix but let's keep this issue open until the proper fix is merged.
@baentsch Isn't this done already?
@baentsch Isn't this done already?
Nope. Only a workaround. New oqsprovider
release has only recently been done. Will do PR to fix this for good this week.
Fixed
Please see: https://github.com/openssl/openssl/actions/runs/10906210475/job/30266951906