Age | Commit message (Collapse) | Author | Files | Lines |
|
The "exploitable vulnerability" may lead to a misunderstanding that
missed hardening issues are considered vulnerabilities, just that
they're not exploitable. This is not true, since while hardening bugs
may be security-relevant, the absence of hardening does not make a
program any more vulnerable to exploits than without.
Drop the "exploitable" word to make it clear that missed hardening is
not considered a vulnerability.
Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
ChangeLog:
* SECURITY.txt: Drop "exploitable" in the hardening section.
|
|
86% of the document have 4 spaces; adjust the remaining 14%.
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
ChangeLog:
* SECURITY.txt: Fix up indentation.
|
|
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
ChangeLog:
* SECURITY.txt: Fix up commas.
|
|
Define a security process and exclusions to security issues for GCC and
all components it ships.
Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
ChangeLog:
* SECURITY.txt: New file.
|