-
-
Notifications
You must be signed in to change notification settings - Fork 7k
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
[Feature Request] Theme CSP nonce should be removed #15973
Comments
+1 for this. A nonce should not be a fixed value. FWIW I managed to load Vuetify at build time and generate a CSP. |
So, I don't think this was a good idea to have closed this issue. I saw several users asking for help to solve unsafe-inline issue for style on vuetify discord and they are often encouraged to use the current "nonce" way.
This also makes sense to me. |
(I add link to a related discord discussion : https://discord.com/channels/340160225338195969/1143844905660190790) |
(Just in case, I ping @johnleider) |
Problem to solve
Theme
cspNonce
gives sense of false security. The nonce should be regenerated for every request or it is really not any more secure than unsafe-inline as the attacker could use the static nonce in their payload.Proposed solution
The only real solutions are to either use a CSP hash or not generate a theme at all.
This should be documented so people find the correct solution.
The generated theme hash should not change between builds so it would need to be regenerated only if theme configuration changes.
The text was updated successfully, but these errors were encountered: