-
Notifications
You must be signed in to change notification settings - Fork 5k
feat(fips): do not allow scram sasl mechanism in fips mode #43062
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
Conversation
scram is using custom implementation of pbkdf2 which is not allowed in fips mode
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
@kruskall how did you detect this issue? Any tooling that you used for it given that it is not stdlib implementation? |
|
nope, just spotted the dependency since it was linked in the final binary |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
mauri870
left a comment
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.
Code-wise, it looks fine, but I'm not experienced with SASL and Kafka to provide a meaningful review. The history of this file is quite shallow, so I can't find any previous developers to ping.
* feat(fips): do not allow scram sasl mechanism in fips mode scram is using custom implementation of pbkdf2 which is not allowed in fips mode * Update sasl_fips.go * Update sasl_fips.go (cherry picked from commit 9761c36)
* feat(fips): do not allow scram sasl mechanism in fips mode scram is using custom implementation of pbkdf2 which is not allowed in fips mode * Update sasl_fips.go * Update sasl_fips.go (cherry picked from commit 9761c36)
…43204) * feat(fips): do not allow scram sasl mechanism in fips mode scram is using custom implementation of pbkdf2 which is not allowed in fips mode * Update sasl_fips.go * Update sasl_fips.go (cherry picked from commit 9761c36) Co-authored-by: kruskall <[email protected]>
…43203) * feat(fips): do not allow scram sasl mechanism in fips mode scram is using custom implementation of pbkdf2 which is not allowed in fips mode * Update sasl_fips.go * Update sasl_fips.go (cherry picked from commit 9761c36) Co-authored-by: kruskall <[email protected]>
Proposed commit message
scram is using custom implementation of pbkdf2 which is not allowed in fips mode
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs