Skip to content

[SRI Message Signatures] Require an enforceable Unencoded-Digest.#59089

Draft
chromium-wpt-export-bot wants to merge 1 commit intomasterfrom
chromium-export-cl-7734936
Draft

[SRI Message Signatures] Require an enforceable Unencoded-Digest.#59089
chromium-wpt-export-bot wants to merge 1 commit intomasterfrom
chromium-export-cl-7734936

Conversation

@chromium-wpt-export-bot
Copy link
Copy Markdown
Collaborator

If the Unencoded-Digest header contains an unknown algorithm, we can't
enforce its assertions on the content we download. This enables forward
compatibility with new algorithms, but also opens a hole in signature
checks, insofar as the signature over an unenforceable digest is equally
unenforceable. Here, we follow the spec change in 1 to require
enforcability.

Bug: 498080391
Change-Id: I7422e261831cd1af0da9fb97c603350733cff262

Reviewed-on: https://chromium-review.googlesource.com/7734936
WPT-Export-Revision: ab476a84fcd9bb2a67bb7b51ffedb60c61ca89ad

If the `Unencoded-Digest` header contains an unknown algorithm, we can't
enforce its assertions on the content we download. This enables forward
compatibility with new algorithms, but also opens a hole in signature
checks, insofar as the signature over an unenforceable digest is equally
unenforceable. Here, we follow the spec change in [1] to require
enforcability.

[1]: WICG/signature-based-sri@c6300af

Bug: 498080391
Change-Id: I7422e261831cd1af0da9fb97c603350733cff262
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants