Enhancement/5039 remove x crypto fips#7072
Conversation
|
This pull request does not have a backport label. Could you fix it @kaanyalti? 🙏
|
65d0fb3 to
8e74a0a
Compare
|
Blocked until go version can be bumped up to 1.24 |
df255d7 to
8d17eea
Compare
8d17eea to
ecea4ae
Compare
|
unblocked, go version bumped is merged |
kruskall
left a comment
There was a problem hiding this comment.
LGTM!
just a minor question for the agent team
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
pchila
left a comment
There was a problem hiding this comment.
Looks good, we just need to split off the beats bump to a separate PR and remove the changelog.
Waiting for a green CI before approval
ecea4ae to
978420a
Compare
|
This pull request is now in conflicts. Could you fix it? 🙏 |
db2dc3e to
573d9d8
Compare
swiatekm
left a comment
There was a problem hiding this comment.
LGTM. Left a comment about moving values to named constants, but I'm ok with this being merged without it having been addressed.
|
This pull request is now in conflicts. Could you fix it? 🙏 |
8aa3577 to
cae5b1a
Compare
f1df84d to
f4dd9cb
Compare
|
* enhancement(5039): replace x/crypto/pbkdf2 with stdlib pbkdf2 * enhancement(5039): added nolint comment (cherry picked from commit 33df025)
* enhancement(5039): replace x/crypto/pbkdf2 with stdlib pbkdf2 * enhancement(5039): added nolint comment (cherry picked from commit 33df025)




What does this PR do?
Removes x/crypto usage
Why is it important?
We need to move away from using x/crypto for fips compliance
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testDisruptive User Impact
None
How to test this PR locally
Ci tests should be enough
Related issues