From: "Rodrigo Rubira Branco" <rbranco@la.checkpoint.com>
To: <linux-kernel@vger.kernel.org>, <stable@kernel.org>
Cc: <greg@kroah.com>, "'Justin Forbes'" <jmforbes@linuxtx.org>,
"'Zwane Mwaikambo'" <zwane@arm.linux.org.uk>,
"'Theodore Ts'o'" <tytso@mit.edu>,
"'Randy Dunlap'" <rdunlap@xenotime.net>,
"'Dave Jones'" <davej@redhat.com>,
"'Chuck Wolber'" <chuckw@quantumlinux.com>,
"'Chris Wedgwood'" <reviews@ml.cw.f00f.org>,
"'Michael Krufky'" <mkrufky@linuxtv.org>,
"'Chuck Ebbert'" <cebbert@redhat.com>,
"'Domenico Andreoli'" <cavokz@gmail.com>,
"'Willy Tarreau'" <w@1wt.eu>, <torvalds@linux-foundation.org>,
<akpm@linux-foundation.org>, <alan@lxorguk.ukuu.org.uk>,
"'Alan Cox'" <alan@redhat.com>, <caglar@pardus.org.tr>,
"'Greg KH'" <gregkh@suse.de>, <casey@schaufler-ca.com>
Subject: Re: [stable] Linux 2.6.25.10 (resume)
Date: Wed, 16 Jul 2008 01:01:24 -0300 [thread overview]
Message-ID: <005001c8e6f8$ac0955f0$a6181fac@ad.checkpoint.com> (raw)
In-Reply-To: <200807021809.07679.caglar@pardus.org.tr>
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.
Don't really matter to us what the policy is, but it's really important to
follow it (many people, who are security professionals need that, and many
others, who are NOT security professionals also).
We all know (both sides) that it's impossible to know everything related to
every bug and it's security impact. But there is a lot of different
situations well-known as a security problems (because the bug class is well
know, because someone reported it with details to the devels, etc). Hide it
is an option, disclouse it is another. Have a policy is what matters. Say
something and do another thing is always bad to everybody involved.
P.S: I'm talking by myself, not for the company that I work for.
Rodrigo Rubira Branco (BSDaemon).
next prev parent reply other threads:[~2008-07-16 4:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080701151057.930340322@mini.kroah.org>
2008-07-01 15:18 ` [patch 0/9] 2.6.25.10 -stable review Greg KH
2008-07-01 15:18 ` [patch 1/9] TTY: fix for tty operations bugs Greg KH
2008-07-01 16:01 ` Greg KH
2008-07-02 9:57 ` S.Çağlar Onur
2008-07-02 9:44 ` Alan Cox
2008-07-02 14:41 ` Greg KH
2008-07-02 15:09 ` S.Çağlar Onur
2008-07-16 4:01 ` Rodrigo Rubira Branco [this message]
2008-07-16 4:49 ` [stable] Linux 2.6.25.10 (resume) Greg KH
2008-07-18 14:07 ` Rodrigo Rubira Branco (BSDaemon)
2008-07-18 15:20 ` Willy Tarreau
2008-07-18 15:29 ` Rodrigo Rubira Branco (BSDaemon)
2008-07-19 4:45 ` david
2008-07-19 10:11 ` Alan Cox
2008-07-22 0:48 ` Rodrigo Rubira Branco (BSDaemon)
2008-07-23 4:27 ` Greg KH
2008-07-23 11:54 ` pageexec
2008-07-23 14:31 ` Henrique de Moraes Holschuh
2008-07-23 14:53 ` pageexec
2008-07-19 22:13 ` Greg KH
2008-07-20 17:28 ` Al Viro
2008-07-22 1:07 ` Rodrigo Rubira Branco (BSDaemon)
2008-07-22 0:52 ` Rodrigo Rubira Branco (BSDaemon)
2008-07-01 15:19 ` [patch 2/9] futexes: fix fault handling in futex_lock_pi Greg KH
2008-07-01 15:19 ` [patch 3/9] IB/mthca: Clear ICM pages before handing to FW Greg KH
2008-07-01 15:19 ` [patch 4/9] DRM: enable bus mastering on i915 at resume time Greg KH
2008-07-01 15:19 ` [patch 5/9] x86_64 ptrace: fix sys32_ptrace task_struct leak Greg KH
2008-07-01 15:19 ` [patch 6/9] sched: fix cpu hotplug Greg KH
2008-07-01 15:19 ` [patch 7/9] ptrace GET/SET FPXREGS broken Greg KH
2008-07-01 15:19 ` [patch 8/9] x86: fix cpu hotplug crash Greg KH
2008-07-01 15:19 ` [patch 9/9] x86: shift bits the right way in native_read_tscp Greg KH
2008-07-01 16:43 ` [patch 0/9] 2.6.25.10 -stable review Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005001c8e6f8$ac0955f0$a6181fac@ad.checkpoint.com' \
--to=rbranco@la.checkpoint.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=caglar@pardus.org.tr \
--cc=casey@schaufler-ca.com \
--cc=cavokz@gmail.com \
--cc=cebbert@redhat.com \
--cc=chuckw@quantumlinux.com \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jmforbes@linuxtx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=rdunlap@xenotime.net \
--cc=reviews@ml.cw.f00f.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
--cc=zwane@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox