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.
π‘οΈ Sentinel: [CRITICAL] Fix timing attack vulnerability in secret comparisons #43
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
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
π‘οΈ Sentinel: [CRITICAL] Fix timing attack vulnerability in secret comparisons #43
Changes from all commits
7da0f77File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
Hono's
timingSafeEqualutility natively supports raw strings of different lengths. Internally, it automatically converts strings toUint8ArrayusingTextEncoderand hashes both inputs using SHA-256 before performing a constant-time comparison.Because of this, manually instantiating
TextEncoderand encoding the strings beforehand is redundant and adds unnecessary overhead. We can safely revert to passing the raw strings directly.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 with the webhook verification, Hono's
timingSafeEqualnatively handles raw strings by encoding and hashing them internally. Manually encodingexpectedandprovidedwithTextEncoderis redundant. We can simplify this check by passing the strings directly.Uh oh!
There was an error while loading. Please reload this page.