Repository navigation
JavaScript SDK: fall back to the default key when unsupported, and validate caller-supplied server public key ids (KSM-1256) #1143
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
Closed
stas-schaller
wants to merge
4
commits into
release/sdk/javascript/core/v17.6.0
from
feature/KSM-1256-js-transmission-key-fallback
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
71bfe27
fix(javascript): fall back to the default key when the stored server …
stas-schaller 2c4784e
fix(javascript): self-heal a corrupted serverPublicKeyId back to the …
stas-schaller a48b754
fix(javascript): stop persisting the transmission-key fallback, valid…
stas-schaller 39ec0c7
fix(javascript): validate caller-supplied ids before persisting, deri…
stas-schaller 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
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
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.
Pre-existing gap in this same function, flagging since this PR touches it: this branch returns
publicKeyId: keyNumberwith no validation.keyNumberisNumber(keyNumberString)(line 753), so a non-numericserverPublicKeyIdpaired with a setserverPublicKeyyieldspublicKeyId: NaNhere, which gets sent verbatim as thePublicKeyIdheader ('NaN') inpostFunction. The PR description calls the pinned custom-key path unaffected, but it has the same class of bug this PR just fixed on the other branch.