-
Notifications
You must be signed in to change notification settings - Fork 95
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
[JEP-237] disable escapeHatch when Jenkins is in FIPS mode #418
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #418 +/- ##
============================================
- Coverage 71.88% 71.77% -0.12%
- Complexity 206 208 +2
============================================
Files 16 16
Lines 900 907 +7
Branches 126 126
============================================
+ Hits 647 651 +4
- Misses 186 189 +3
Partials 67 67 ☔ View full report in Codecov by Sentry. |
let's be honest Codecov is useless here.... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should add a test proving that in CasC the escape hatch cannot be configured.
oops I forgot a test class :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as per https://github.com/jtnord/oic-auth-plugin/pull/1/files, this check should be included in the readresolve
done with 4623768 |
df6e4dd
to
1f77826
Compare
Signed-off-by: Olivier Lamy <[email protected]>
1f77826
to
ea9366c
Compare
Signed-off-by: Olivier Lamy <[email protected]>
The escapeHatch login uses a non compliant encryption library (along with an non compliant encryption algotithm) (
BCrypt
) for storing the escape hatch password.Whilst some equivallent functionality could be written (storing the password in PBKDF2 for example), the security implications on a back-door user in a FIPS compliant setup would be questionable.
Therefor this PR just disables the ability to create or use the escapeHatch when Jenkins is in FIPS mode.
This PR does not mean that the plugin is now FIPS compliant, it just makes it one step closer to be by removing one blocker.
Signed-off-by: Olivier Lamy [email protected]
Testing done
Submitter checklist