script: Use base64ct instead of base64 in SubtleCrypto
#40334
Merged
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.
The
SubtleCryptointerface of WebCrypto API needs to encode and decode keys in base64 alphabets when exporting/importing keys in JsonWebKey format.We currently use the
base64crate to handle base64 encoding and decoding. This patch switches to use thebase64ctcrate, which is a constant-time implementation of base64 alphabets.Using constant-time implementation to handle base64 encoding and decoding of cryptographic secret provides a better protection against time-based sidechannel attack.
Remarks: The multi-line changes in
ecdh_operation.rsare mostly caused by./mach fmt.Testing: Refactoring. Existing tests suffice.