linux-kernel - Re: [stable] Linux 2.6.25.10 (resume)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 19 Jul 2008 15:13:43 -0700
From:	Greg KH <gregkh@...e.de>
To:	"Rodrigo Rubira Branco (BSDaemon)" <rbranco@...CHECKPOINT.COM>
Cc:	linux-kernel@...r.kernel.org, stable@...nel.org, greg@...ah.com,
	'Justin Forbes' <jmforbes@...uxtx.org>,
	'Zwane Mwaikambo' <zwane@....linux.org.uk>,
	'Theodore Ts'o' <tytso@....edu>,
	'Randy Dunlap' <rdunlap@...otime.net>,
	'Dave Jones' <davej@...hat.com>,
	'Chuck Wolber' <chuckw@...ntumlinux.com>,
	'Chris Wedgwood' <reviews@...cw.f00f.org>,
	'Michael Krufky' <mkrufky@...uxtv.org>,
	'Chuck Ebbert' <cebbert@...hat.com>,
	'Domenico Andreoli' <cavokz@...il.com>,
	'Willy Tarreau' <w@....eu>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
	'Alan Cox' <alan@...hat.com>, caglar@...dus.org.tr,
	casey@...aufler-ca.com, spender@...ecurity.net,
	pageexec@...email.hu, rodrigo@...nelhacking.com
Subject: Re: [stable] Linux 2.6.25.10 (resume)

On Fri, Jul 18, 2008 at 11:07:45AM -0300, Rodrigo Rubira Branco (BSDaemon) wrote:
> --- 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.

I guess what is getting everyone's panties all in a bind is the term
"disclosed", right?  Why not just drop this word from the sentence
instead of rewording it so much?

> @@ -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.

I don't see why this needs to be changed, sometimes we do release
exploit code to third parties that ask us nicely and the reporter allows
us to.

>  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.

Ah, again, it's the "fully disclose" that is causing panties to ride
high.  And again, we are disclosing the bug with the real fix and the
code in question.  We just seem to differ on what people consider
"fully" it seems.  I think the people liking that term these days
consider that you must release exploit and other detailed information.

I disagree with this and feel that our current policy of fixing bugs and
releasing full code is pretty much the same thing as we are doing today,
although I can understand the confusion.  How about this rewording of
the sentance instead:

	We prefer to fix and provide an update for the bug as soon as
	possible.

So a simple 1 line change should be enough to stem this kind of argument
in the future, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/