rfc:security-classification
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:security-classification [2016/11/11 12:51] – krakjoe | rfc:security-classification [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2016-11-10 | * Date: 2016-11-10 | ||
* Authors: Release Managers | * Authors: Release Managers | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
At the end of last month, Stas posted to internals with some ideas to reform security issue [[http:// | At the end of last month, Stas posted to internals with some ideas to reform security issue [[http:// | ||
- | Current | + | Currently |
In short, all the security issues can be split into three groups with high, medium and low severity. The essential idea of such classification definitions is to allow different handling depending on the issue severity. In practice, the majority of security issues are purely theoretical, | In short, all the security issues can be split into three groups with high, medium and low severity. The essential idea of such classification definitions is to allow different handling depending on the issue severity. In practice, the majority of security issues are purely theoretical, | ||
Line 23: | Line 23: | ||
Voting opened November 11th for one week, closing November 18th: | Voting opened November 11th for one week, closing November 18th: | ||
- | <doodle title=" | + | <doodle title=" |
* Yes | * Yes | ||
* No | * No |
rfc/security-classification.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1