|
From: | Florian Weimer |
Subject: | Re: Document hardening flags in the coding standards |
Date: | Fri, 06 Jul 2012 09:40:34 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 |
On 07/06/2012 12:17 AM, Karl Berry wrote:
First: rms asked "what do they do?". And I guess that is what I am wondering too, to find the right place.
They turn bugs which would result in code execution into mere crashers (most of the time). We hope that this gives developers time to work on a real fix if a new bug comes up.
Well, the coding standards doesn't seem like the place for the primary documentation of a gcc/glibc/kernel/whatever feature. If someone says "how do I use GCC to make my program more secure", it doesn't seem like the answer should be in standards.texi.
There is a precedent, and I thought it could be expanded: http://www.gnu.org/prep/standards/html_node/Semantics.html That's why I thought the coding standards would be the relevant document. -- Florian Weimer / Red Hat Product Security Team
[Prev in Thread] | Current Thread | [Next in Thread] |