Security and Functional Flaw Reporting » History » Version 7
Andreas Steffen, 23.05.2013 13:09
Describe security flaw handling process
h1. Security and Functional Flaw Reporting
h2. Security Flaws
* Please email any security-relevant flaw to the special mail account *firstname.lastname@example.org*. Whenever possible encrypt your posting using the "PGP key":http://pgp.mit.edu:11371/pks/lookup?search=security%40strongswan.org for the *email@example.com* account.
* For high and medium severity vulnerabilities we are going to apply for a CVE number first. Next we notify all known strongSwan customers and the major Linux distributions, giving them a time of about three weeks to patch their their software release. On predetermined date we officially issue a patch for the vulnerability and usually a new stable strongSwan release containing the security fix. Also the CVE entry will published.
* Minor vulnerabilities usually will be fixed immediately and the corresponding patch will be posted on the strongSwan mailing list.
* Here is the list of all reported strongSwan high and medium security flaws registered in the "CVE database":http://web.nvd.nist.gov/view/vuln/search-results?query=strongswan which were fixed by the following "security patches":http://download.strongswan.org/security/.
h2. Functional Flaws
* Please report all non-security-related flaws and bugs by opening a "new issue":http://wiki.strongswan.org/projects/strongswan/issues/new in our wiki. If you don't have a user account yet, please "register":http://wiki.strongswan.org/account/register first.
* Our Redmine Tracker classifies user issues into the following three categories:
* *Issue*: Please choose this generic category if you are not sure whether your problem is caused by a strongSwan misconfiguration, an interoperability problem with third party VPN software or an actual bug in the strongSwan code. We are going to reclassify your report after a first analysis.
* *Feature*: Please choose this category for requesting new features that we might implement in future versions of the strongSwan software.
* *Bug*: Please post under this category only if you are quite sure that you identified a bug in the strongSwan code, e.g. if the charon daemon crashes which it shouldn't. Of course it is helpful if you can already pinpoint the code file where you suspect the bug or in the case of a crash to provide a backtrack analysis of the core dump. User patches fixing flaws are always welcome.