-
Notifications
You must be signed in to change notification settings - Fork 25k
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
SSL related tests failures with BCJSSE in FIPS 140 mode #49094
Comments
Pinging @elastic/es-security (:Security/Network) |
Cause is tracked in elastic#49094
Another case is |
Cause is tracked in elastic#49094 Backport of elastic#51992
I also saw
Unfortunately I couldn't reproduce this locally. |
Thanks @dliappis ! In the above, the
so this is not related to the kind of failures we are tracking here. The reproduction line is from |
Ugh my mistake, sorry. Will update the repro. |
I have updated the above repro it doesn't reproduce locally though. @jkakavas do you think it makes sense to track this in a separate bug? |
It has failed exactly once with this and I believe that the TLS exceptions might be a symptom and not the cause here. I will keep track of this for the next couple of days but since it doesn't reproduce, I don't think we should mute or track this in an issue for now |
I caught a similar report as the one from @dliappis on CI this morning:
with the following test failing:
But doesn't repro for me.
Build scan https://gradle-enterprise.elastic.co/s/anyrby5ddynwq |
These are all unrelated to the problem this issue is tracking, so can we open a new issue so that we don't miss it? |
Pinging @elastic/es-security (Team:Security) |
This issue has been closed because it has been open for too long with no activity. Any muted tests that were associated with this issue have been unmuted. If the tests begin failing again, a new issue will be opened, and they may be muted again. |
Reopening. The tests are still muted in FIPS mode. We should unmute them and see if we still get failures. |
Fixes and un-mutes tests associated with FIPS. Most of the fixes are due to differing expected exceptions or log messages when using BouncyCastle as the JCE/JSSE provider. Only test code is changed with this commit. fixes: elastic#49094
Example build scan: https://gradle-enterprise.elastic.co/s/i5x2i3udx2ifg
all fail when using BCJSSE in FIPS 140 mode.
For
the SSL handshake should fail but we would expect an exception similar to the
SSLHandshakeException
that SunJSSE throws.shouldn't throw an exception at all.
All three of them cause the following stacktrace
which seems to indicate that the certificate signature cannot be verified by the JSSE provider ( regardless of the trust ) which is rather unexpected. It is not entirely obvious if this fails because of BCJSSE being in FIPS mode or because of simply using BCJSSE instead of SunJSSE, as we only use BCJSSE to run our FIPS 140 tests.
I've muted these 3 tests for now until we have a solution or resolution in place
The text was updated successfully, but these errors were encountered: