Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

we need a security policy #576

Closed
chadwhitacre opened this issue Jan 31, 2013 · 4 comments
Closed

we need a security policy #576

chadwhitacre opened this issue Jan 31, 2013 · 4 comments

Comments

@chadwhitacre
Copy link
Contributor

http://news.ycombinator.com/item?id=5141299

do sec people inherently know to try hitting /security.html by convention, or should there be links to it from the main site?

They know to look for a link to the security page.
Github's is in their site footer.
37signals' is in their site footer.
Twitter's is linked off the sidebar in their "About" page.
Google's and Facebook's are the top search result for their site and "vulnerability" "security".
These are all fine options.

@sigmavirus24
Copy link
Contributor

I would put it in the site footer so it is available everywhere.

chadwhitacre added a commit that referenced this issue Feb 1, 2013
I went for a text file in the site root.
@patcon
Copy link
Contributor

patcon commented Apr 19, 2014

Reopening this for #2072 (comment)

cc: @greggles

@patcon patcon reopened this Apr 19, 2014
@patcon
Copy link
Contributor

patcon commented Apr 19, 2014

Convo with @clone1018 on internal password policies: IRC

@rummik
Copy link
Contributor

rummik commented Apr 21, 2014

+1-ing this so it doesn't get lost in my GitHub notifications. Security acknowledgements are good, but both that and policy is better

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants