Content Security Policy

[Matt Molyneaux]

CSP (Content Security Policy) is notably missing from MediaGoblin.

This will add an additional layer of security should a user be able to bypass comment sanitisation (or the blogging plugin) and add some hostile JS to their content.

At the very least, we should use this to limit JS to the host static assets are on.

Will be kinda tricky to implement in such a way that it won't cause issues when deploying - especially for novice users.

[Ben Sturmfels]

Hi moggers87,

This sounds like a great suggestion. We could do this either in the Nginx deployment example, or by adding the header to the text/html HTTP responses created by MediaGoblin.

Header would look like this:

Content-Security-Policy: script-src 'self' 'unsafe-inline'

For Nginx, the directive would be:

add_header Content-Security-Policy "script-src 'self' 'unsafe-inline'";

Nginx would be the simplest change (just docs), and you can then be confident that it applies to the whole site. Any thoughts?

Cheers,
Ben