HADOOP-19869 Modernize secret manager default algorithm and key length#8453
HADOOP-19869 Modernize secret manager default algorithm and key length#8453steveloughran wants to merge 1 commit intoapache:trunkfrom
Conversation
HmacSHA256 and 256 bits. Also import directly the algorithm in different modules, so it is consistent.
cnauroth
left a comment
There was a problem hiding this comment.
+1 pending pre-commits. Would this need to target 3.6.0 for compatibility concerns?
|
💔 -1 overall
This message was automatically generated. |
|
@steveloughran as we have set up an alternative is to keep Jenkins as-is and run GHA in parallel until we migrate all jobs to GHA, I'm afraid this will take a long time due to lots of flaky tests (~200 classes) |
|
@pan3793 +1 for retiring jenkins tests GHA can do @cnauroth this can be backported. It's just the defaults, We'd log as incompatible and say you can change back. It only affects the shared secrets between running services (mr AM and workers, for example), and then it is static...the AM doesn't verify it can recreate it, just that it got the same back. only one I am worried about is HDFS and rolling upgrades. Does a change to keylength/algorithm for new shared secrets cause problems? |
This is the situation I had in mind. If we have some HmacSHA1 tokens in flight, and then we restart NameNode with the new configuration, will it start trying to verify the old tokens as HmacSHA1 and hit password mismatches here? |
|
Lets talk to the hdfs people. Its time to update this |
Description of PR
HADOOP-19869 Modernize secret manager default algorithm and key length
HmacSHA256 and 256 bits.
Also import directly the algorithm in different modules, so it is consistent.
Contains content generated by Coplot + Claude Sonnet 4.6
How was this patch tested?
updated test
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?AI Tooling
If an AI tool was used:
where is the name of the AI tool used.
https://www.apache.org/legal/generative-tooling.html