Adding support for CSP script-src safe inline, for SSR state transfer #2549
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
|
This is awesome, thank you so much! |
|
No problem, thank you for the lib! |
|
Great news! @Atinux is this option available for 1.4 or will it be shipped in v2.? |
|
It’s already here with 1.4
…On Mon 23 Apr 2018 at 03:41, Dominic Garms ***@***.***> wrote:
Great news! @Atinux <https://github.com/Atinux> is this option available
for 1.4 or will it be shipped in v2.?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2549 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA3OFEjQPB2WTXVfrl7-Rdddg9MgwYUEks5trTEwgaJpZM4RY4Ca>
.
|
|
great to hear, I think its just missing in the docs: https://nuxtjs.org/api/configuration-render |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
VueJS is fully CSP compliant (script-wise) when using runtime-only builds [1].
Nuxt appears to follow suit, with the single exception that a strict locked-down CSP policy should not allow inline scripts. SSR state transfer relies on inline scripts in a non-avoidable way. The CSP spec allows for inline scripts to be whitelisted by nonce or checksum.
There appears to be an issue open on this topic already: #2422
My solution allows a user to opt in to CSP script compliance by setting the
options.render.cspvariable to eithertrueor an object containing the keyhashAlgorithm. ThehashAlgorithmmay besha256,sha384orsha512per the CSP spec [2] and these three hash algorithms should also be supported in most builds of Node (it is technically dependent on the version of OpenSSL on the platform, but these are three very common algorithms [3]). The default value issha256if the user just sets the option to true.[1] https://vuejs.org/v2/guide/installation.html#CSP-environments
[2] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src
[3] https://nodejs.org/api/crypto.html#crypto_class_hash