-
Notifications
You must be signed in to change notification settings - Fork 551
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
msquic does not load with OpenSSL in FIPS mode #3422
Comments
It doesn't even export |
question for OpenSSL bit it does not. I think that is same for other ciphers you disable during configuration. If you build without them they just disappear. This should be easy to fix. I have change that would fix it. I'll put up PR when I clean it up and do more testing. |
I'd rather not disable ChaCha20 at build time, but instead dynamically resolve it at runtime. Most folks that use libmsquic package likely won't be FIPS, and I want the algorithm to continue to work. |
yep. since we already have the XXX_HANDLE |
I did more testing and #3423 is unfortunately not sufficient. |
@wfurt can we resolve this now? |
I was planning to close as soon as this rolls in to our tests. I know MsQuic may not care @nibanks but it saves us double tracking. |
If you have something you want/need backported, please just go ahead and create the PR to the correct branch. |
@wfurt have you backported everything you need? I'd like to get this item closed. |
no. I was hoping to flow this to our tests but I'm falling to build MsQuic on Centos 7 because of compiler (and other differences). At this point I'm inclined to just do the port to 2.1 without end to end validation if that is ok with you @nibanks. Is there some timeline for 2.1.8? |
.NET tests are now passing on Mariner 2.0 using 2.1.8
|
Describe the bug
This impacts Centos 7 and Mariner 2.0 (OpenSSL 1.1.1k FIPS) and perhaps other Linux versions.
the load fails as
CHACHA is not approved algorithm and it is missing in system crypto binaries.
This seems to defeat only purpose of
UseSystemOpenSSLCrypto
option.Affected OS
Additional OS information
Centos 7 and Mariner 2.0
MsQuic version
release/2.1
Steps taken to reproduce bug
Try to load published msquic library on impacted OS.
Expected behavior
libmsquic loads and ignores unsupported algorithms. If only CHACHA was requested via policy, API calls should return proper error.
Actual outcome
libmsuic fails to load because of missing dependencies.
Additional details
we should make
QUIC_ALLOWED_CIPHER_SUITE_CHACHA20_POLY1305_SHA256
fully optional. (and related code)cc: @ManickaP @CarnaViire
The text was updated successfully, but these errors were encountered: