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

Content Security Policy headers #41

Open
zackmdavis opened this issue Mar 26, 2015 · 0 comments
Open

Content Security Policy headers #41

zackmdavis opened this issue Mar 26, 2015 · 0 comments
Assignees

Comments

@zackmdavis
Copy link
Owner

Of course we'd rather Finetooth not have any cross-site-scripting exploits, but if the measures implemented in 35d8662 turn out to have any loopholes, we can at least prevent attackers from doing anything terribly interesting with them. There are third-party apps for this, but it looks sufficiently straightforward that I'd rather avoid dependency bloat by Inventing It Here.

@zackmdavis zackmdavis self-assigned this Aug 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant