| (__| |_| | _ <| |___
\___|\___/|_| \_\_____|
-CURL SECURITY FOR DEVELOPERS
+curl security for developers
+============================
This document is intended to provide guidance to curl developers on how
security vulnerabilities should be handled.
-PUBLISHING INFORMATION
+Publishing Information
+----------------------
-All known and public curl or libcurl related vulnerabilities are listed at
-http://curl.haxx.se/docs/security.html
+All known and public curl or libcurl related vulnerabilities are listed on
+[the curl web site security page](http://curl.haxx.se/docs/security.html).
Security vulnerabilities should not be entered in the project's public bug
tracker unless the necessary configuration is in place to limit access to the
issue to only the reporter and the project's security team.
-VULNERABILITY HANDLING
+Vulnerability Handling
+----------------------
The typical process for handling a new security vulnerability is as follows.
announcement.
- The person discovering the issue, the reporter, reports the vulnerability
- privately to curl-security@haxx.se. That's an email alias that reaches a
+ privately to `curl-security@haxx.se`. That's an email alias that reaches a
handful of selected and trusted people.
- Messages that do not relate to the reporting or managing of an undisclosed
- Write a security advisory draft about the problem that explains what the
problem is, its impact, which versions it affects, solutions or
- work-arounds, when the release is out and make sure to credit all
+ workarounds, when the release is out and make sure to credit all
contributors properly.
-- Request a CVE number from distros@openwall.org[1] when also informing and
+- Request a CVE number from distros@openwall[1] when also informing and
preparing them for the upcoming public security vulnerability announcement -
attach the advisory draft for information. Note that 'distros' won't accept
an embargo longer than 19 days.
the same manner we always announce releases. It gets sent to the
curl-announce, curl-library and curl-users mailing lists.
-- The security web page on the web site should get the new vulernability
+- The security web page on the web site should get the new vulnerability
mentioned.
[1] = http://oss-security.openwall.org/wiki/mailing-lists/distros
+
+CURL-SECURITY (at haxx dot se)
+------------------------------
+
+Who is on this list? There are a couple of criteria you must meet, and then we
+might ask you to join the list or you can ask to join it. It really isn't very
+formal. We basically only require that you have a long-term presence in the
+curl project and you have shown an understanding for the project and its way
+of working. You must've been around for a good while and you should have no
+plans in vanishing in the near future.
+
+We do not make the list of partipants public mostly because it tends to vary
+somewhat over time and a list somewhere will only risk getting outdated.