Re: [stable] Linux 2.6.25.10 (resume)

["Rodrigo Rubira Branco (BSDaemon)" <rbranco@LA.CHECKPOINT.COM>]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Greg KH escreveu:
> On Wed, Jul 16, 2008 at 01:01:24AM -0300, Rodrigo Rubira Branco wrote:
>   
>> First of all sorry for copy many people who maybe are not in the initial
>> discussion, but since I've not been copied I have no idea who are and who
>> are not in that thread ;)
>>
>> The point that many people are trying to make is that Linux has a policy
>> defined in a document (Documentation/SecurityBugs) but are not following it.
>>     
>
> {sigh}
>
> Are you sure?  What specific sentance(s) are you saying that we are not
> currently following.  And if not, can you propose a patch to the file to
> properly reflect how you seem to think we currently are working?
>
>   
Attached ;)  Please, let me know what do you think.

> getting very annoyed at people saying I am somehow doing the job I do
> for free, on my own time, incorrectly,
>
> greg k-h
>   
For free? Hum, let's forget that you work as a linux developer... we are
also trying to contribute in some way for free...


P.S:  It's obvious that my opinions are mine, not of my employer ;)




[-- Attachment #2: SecurityBugs.patch --]
[-- Type: text/plain, Size: 2497 bytes --]

--- SecurityBugs.orig	2008-07-16 23:46:09.000000000 -0300
+++ SecurityBugs	2008-07-17 14:58:32.000000000 -0300
@@ -1,7 +1,7 @@
-Linux kernel developers take security very seriously.  As such, we'd
-like to know when a security bug is found so that it can be fixed and
-disclosed as quickly as possible.  Please report security bugs to the
-Linux kernel security team.
+Linux kernel developers take security very seriously, in exactly the 
+same way we do with any other bugs.  As such, we'd like to know when 
+a security bug is found so that it can be fixed as soon as possible.
+Please report security bugs to the Linux kernel security team.
 
 1) Contact
 
@@ -14,23 +14,24 @@
 As it is with any bug, the more information provided the easier it
 will be to diagnose and fix.  Please review the procedure outlined in
 REPORTING-BUGS if you are unclear about what information is helpful.
-Any exploit code is very helpful and will not be released without
-consent from the reporter unless it has already been made public.
+Any exploit code is very helpful and will not be released.
 
 2) Disclosure
 
 The goal of the Linux kernel security team is to work with the
 bug submitter to bug resolution as well as disclosure.  We prefer
-to fully disclose the bug as soon as possible.  It is reasonable to
+to not disclose the bug, since we believe any kind of bug deserves the
+same attention and will be quickly patched.  It is reasonable to
 delay disclosure when the bug or the fix is not yet fully understood,
 the solution is not well-tested or for vendor coordination.  However, we
 expect these delays to be short, measurable in days, not weeks or months.
 A disclosure date is negotiated by the security team working with the
-bug submitter as well as vendors.  However, the kernel security team
-holds the final say when setting a disclosure date.  The timeframe for
-disclosure is from immediate (esp. if it's already publically known)
-to a few weeks.  As a basic default policy, we expect report date to
-disclosure date to be on the order of 7 days.
+bug submitter as well as vendors if the submitter wants to disclose.  
+However, the kernel security team holds the final say when setting a 
+disclosure date.  The timeframe for disclousure is from immediate (esp. if
+it's already publically known) to a few weeks.  As a basic default policy,
+we expect report date to disclosure (if the submitter requires disclosure)
+to be on the order of 7 days.
 
 3) Non-disclosure agreements