Skip to content
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

[6.7] Introduce content security policy (CSP) (#29545) #30686

Merged
merged 1 commit into from
Feb 11, 2019

Conversation

epixa
Copy link
Contributor

@epixa epixa commented Feb 11, 2019

Backports the following commits to 6.7:

* csp: nonce and unsafe-eval for scripts

To kick things off, a rudimentary CSP implementation only allows
dynamically loading new JavaScript if it includes an associated nonce
that is generated on every load of the app.

A more sophisticated content security policy is necessary, particularly
one that bans eval for scripts, but one step at a time.

* img-src is not necessary if the goal is not to restrict

* configurable CSP owned by security team

* smoke test

* remove x-content-security-policy

* document csp.rules

* fix tsconfig for test

* switch integration test back to regular js

* stop looking for tsconfig in test

* grrr, linting errors not caught by precommit

* docs: people -> you for consistency sake

Co-Authored-By: epixa <court@epixa.com>
@epixa epixa added the backport label Feb 11, 2019
@epixa epixa self-assigned this Feb 11, 2019
@elasticmachine
Copy link
Contributor

💔 Build Failed

@epixa
Copy link
Contributor Author

epixa commented Feb 11, 2019

All of the jobs in CI went green, but there was a jenkins error in the parent job which flagged the whole build as red.

@epixa epixa merged commit 8461561 into elastic:6.7 Feb 11, 2019
@epixa epixa deleted the backport/6.7/pr-29545 branch February 11, 2019 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants