-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update test server with liboqs 0.10.0 release #271
Comments
#261 QUIC I wonder if we can combine QUIC server (based on OQS-BoringSSL) and Nginx together, then it'll be easier for us to maintain. |
Never mind. We still need oqs-provider to create and sign certificates anyway. |
@pi-314159 I think it's a great idea to add some QUIC-enabled ports to the test server. I'm ok if this means maintaining nginx-openssl and nginx-boringssl at the moment. Re. the server update: with open-quantum-safe/oqs-provider#386 merged, I'll go ahead updating the server to liboqs-0.10.0 and will then have a look at QUIC. |
It may be more efficient to do a full release of |
@bhess QUIC hasn’t been updated. I’ll update QUIC and create a new Dockerfile next month when I have time. Let’s leave it as-is for this release. |
TWIMC, oqs-provider 0.6.0 is available as RC1; without comments to the contrary I'll turn this into final release before leaving on vacation at the end of this week. |
Thanks @baentsch. I've updated the server and the corresponding build script. All tests pass. See #272. I'll update the PR pointing to the final oqs-provider release before merging. |
According to @bhess this has been resolved, so closing this issue. |
No description provided.
The text was updated successfully, but these errors were encountered: