Skip to content

Implement Security Headers #586

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

Closed
1 of 5 tasks
ghost opened this issue Mar 3, 2017 · 0 comments
Closed
1 of 5 tasks

Implement Security Headers #586

ghost opened this issue Mar 3, 2017 · 0 comments
Labels
A-backend ⚙️ C-bug 🐞 Category: unintended, undesired behavior E-help-wanted

Comments

@ghost
Copy link

ghost commented Mar 3, 2017

Related to #585

As asked by @carols10cents, here's a tasklist on what headers should be implemented.

  • Implement Content Security Policy (CSP) header

  • Implement HTTP Strict Transport Security (HSTS) header

  • Implement X-Content-Type-Options header

  • Implement X-Frame-Options (XFO) header

  • Implement X-XSS-Protection header

sgrif added a commit to sgrif/crates.io that referenced this issue Mar 6, 2017
These headers are all pretty straightforward except CSP. For CSP I
defined the sources based on what was loaded from visiting the main page
and all crates. Images should be safe, so I've allowed them from all
sources.

This should be checked on staging before deploying.

Fixes rust-lang#586.
@carols10cents carols10cents added the C-bug 🐞 Category: unintended, undesired behavior label Aug 2, 2017
carols10cents pushed a commit to sgrif/crates.io that referenced this issue Aug 10, 2017
These headers are all pretty straightforward except CSP. For CSP I
defined the sources based on what was loaded from visiting the main page
and all crates. Images should be safe, so I've allowed them from all
sources.

This should be checked on staging before deploying.

Fixes rust-lang#586.
bors-voyager bot added a commit that referenced this issue Aug 12, 2017
597: Add security headers r=carols10cents

These headers are all pretty straightforward except CSP. For CSP I
defined the sources based on what was loaded from visiting the main page
and all crates. Images should be safe, so I've allowed them from all
sources.

This should be checked on staging before deploying.

Fixes #586.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-bug 🐞 Category: unintended, undesired behavior E-help-wanted
Projects
None yet
Development

No branches or pull requests

1 participant