-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix: strengthen cryptographic operations #19828
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
Open
FrankChen021
wants to merge
12
commits into
apache:master
Choose a base branch
from
FrankChen021:codex/codeql-warning-cryptography
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
1da7b64
fix: strengthen cryptographic operations
FrankChen021 c9c0c48
Suppress legacy cipher validation warning
FrankChen021 d130105
fix: suppress legacy cipher CodeQL alerts
FrankChen021 30e4094
fix: preserve legacy cipher baseline path
FrankChen021 9d6dd16
style: make legacy decryption locals final
FrankChen021 da3f536
docs: clarify legacy cipher validation timing
FrankChen021 beb54f1
fix: preserve legacy cipher baseline location
FrankChen021 8d55057
fix: suppress legacy cipher compatibility alert
FrankChen021 0f4e0ad
fix: attach legacy cipher suppression to declaration
FrankChen021 26dd631
fix: place CodeQL suppression at alert
FrankChen021 b57491d
fix: scope CodeQL suppression to decrypt
FrankChen021 a13febd
chore: remove ineffective CodeQL suppression
FrankChen021 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
[P1] Preserve old-reader compatibility during rolling upgrades
Every encryption now immediately emits the versioned GCM envelope.
CryptoService's only production caller isPac4jSessionStoreon Router nodes, but a pre-upgrade Router interprets the first four magic bytes as the legacy salt length; because that value is negative, it rejects the cookie. With multiple Routers behind a load balancer, a cookie issued by an upgraded Router therefore fails whenever the next request reaches an old Router. Supporting legacy reads only provides old-to-new compatibility, not new-to-old compatibility. Gate GCM writes until all readers are upgraded, retain legacy writes for a transition release, or provide another staged migration mechanism.