Add trusted-types-eval source expression for script-src
#665
Conversation
This file contains 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
3a0f58d
to
8444566
Compare
|
cc @otherdaniel @koto to gather Google feedback. Mozilla Position Request: mozilla/standards-positions#1032 WebKit Position Request: WebKit/standards-positions#355 |
annevk
reviewed
May 31, 2024
8444566
to
824fce9
Compare
trusted-eval source expression for script-srctrusted-types-eval source expression for script-src
824fce9
to
1ed7bc6
Compare
1ed7bc6
to
ad31238
Compare
This new keyword allows enabling eval only when trusted types are enforced. Such that in browsers that don't support trusted types no eval is allowed.
ad31238
to
5b4509b
Compare
|
@mikewest if you've got time it'd be brilliant to get an editorial review of this too. Still waiting on some browser positions so won't merge yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This new keyword allows enabling eval only when trusted types are enforced. Such that in browsers that don't support trusted types no eval is allowed, unlike with
unsafe-eval. This concept was brought up at previous WebAppSec WG meetings.Implementor Interest:
Mozilla (see New
trusted-types-evalkeyword for CSP script-src mozilla/standards-positions#1032)WebKit (see New
trusted-types-evalkeyword for CSP script-src WebKit/standards-positions#355)Chromium - Not sure how best to get an official Google position but Lukas is supportive per New
trusted-types-evalkeyword for CSP script-src WebKit/standards-positions#355 (comment)Preview | Diff