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

Provide a dedicated security package #810

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 3 comments
Closed

Provide a dedicated security package #810

GoogleCodeExporter opened this issue Mar 25, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

There are various things that we can do to improve security in Seaside even 
more:

- provide cryptographically secure session ids
- implement various new HTTP headers 
http://ibuildings.nl/blog/2013/03/4-http-security-headers-you-should-always-be-u
sing

Unfortunately none of those things can be done automatically — they all need 
configuration. Therefore a dedicated security package is warranted.

This issue duplicates Issue 394 and Issue 703

Original issue reported on code.google.com by philippe...@gmail.com on 1 Aug 2014 at 3:10

@GoogleCodeExporter
Copy link
Author

Issue 394 has been merged into this issue.

Original comment by philippe...@gmail.com on 1 Aug 2014 at 3:10

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Issue 703 has been merged into this issue.

Original comment by philippe...@gmail.com on 1 Aug 2014 at 3:10

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by philippe...@gmail.com on 1 Aug 2014 at 3:31

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

@marschall marschall added this to the 3.2 milestone Jul 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants