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
Security disclosure and reporting guidelines #100
Comments
|
ping @dmdj03 @timnguyen can we prioritize this? |
|
Topics: |
|
This is super important, is there anything I can do to help this along? |
|
We should certainly copy Django's policy basically verbatim, Our current page just links to a support page about it, is this going to be an actual page on the site now, or is it going to go there? |
|
Rails' is also pretty good http://rubyonrails.org/security |
|
Taking from Django and Rails: With Rails, we also have a security-announcement only mailing list. We may want to do this, too? |
|
|
|
Looks amazing! Let's do it. |
|
w00t! +1 On Fri, Jan 3, 2014 at 5:24 PM, Steve Klabnik notifications@github.comwrote:
NOTICE: This communication contains privileged or other confidential |
|
@dmdj03 can you please provide the copy and also mark up the image with the various styles that will be used for implementation? e.g. balancedRed100, etc. |


balancedpayments.com has no clear instructions for how to report security issues or vulnerabilities. As prior art we can look at Django's guidelines and Alex Gaynor's general overview of the topic.
The text was updated successfully, but these errors were encountered: