From: david@lang.hm
To: David Schwartz <davids@webmaster.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: RE: [stable] Linux 2.6.25.10
Date: Fri, 18 Jul 2008 18:01:14 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0807181755590.30465@asgard.lang.hm> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKOEJCOEAC.davids@webmaster.com>
On Fri, 18 Jul 2008, David Schwartz wrote:
> Greg KH wrote:
>
>> Personally, I omit posting full "and here is explicitly how to exploit
>> this problem" notices as that is foolish.
>
> That means only people with the time, energy, and expertise to create an
> exploit will have an exploit. This includes probably 90% of the people who
> would use the exploit maliciously
haven't you ever heard of script-kiddies? they are by far the majority of
attacks on systems but do not have the expertise to create exploits. it
takes someone else writing the exploit for them and packaging it to make
them a threat.
in the meantime there's a chance for the fix to get propogated out to a
released version and for people to upgrade their systems. providing
exploit code along with the bugfix means that the script kiddies have the
exploit immediatly, but the fix isn't in any released version (not even a
-rc or daily -git snapshot)
> and 100% of the people who pose a real
> thread to the community.
this depends on how you define threat.
> It does, however, ensure that the majority of
> ordinary users won't be able to test their systems to see if they're
> vulnerable or if the vulnerability is fixed. So at least it will have some
> effect.
how many people run exploits against their production systems to 'see if
they are fixed', very few, and those only on strict schedules with lots of
adnvance notice and other safeguards.
David Lang
next prev parent reply other threads:[~2008-07-19 1:00 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 3:58 Greg KH
2008-07-03 3:58 ` Greg KH
2008-07-03 17:08 ` Bart Van Assche
2008-07-03 17:29 ` Greg KH
2008-07-03 18:57 ` Greg KH
2008-07-03 19:31 ` pageexec
2008-07-14 12:04 ` [stable] " Greg KH
2008-07-15 2:14 ` pageexec
2008-07-15 2:27 ` Linus Torvalds
2008-07-15 15:31 ` pageexec
2008-07-15 16:07 ` Linus Torvalds
2008-07-15 16:13 ` Linus Torvalds
2008-07-17 21:08 ` Aidan Thornton
2008-07-15 19:03 ` pageexec
2008-07-15 19:16 ` Linus Torvalds
[not found] ` <487D20EC.26203.1BD1E5C5@pageexec.freemail.hu>
2008-07-15 20:18 ` Linus Torvalds
2008-07-15 20:23 ` pageexec
2008-07-15 20:42 ` Linus Torvalds
2008-07-15 21:18 ` pageexec
2008-07-15 21:26 ` Linus Torvalds
2008-07-15 22:08 ` pageexec
2008-07-15 23:28 ` Linus Torvalds
2008-07-16 0:00 ` Tiago Assumpcao
2008-07-16 0:16 ` Linus Torvalds
2008-07-16 0:38 ` Tiago Assumpcao
2008-07-16 0:51 ` Linus Torvalds
2008-07-16 1:10 ` Tiago Assumpcao
2008-07-16 1:41 ` Linus Torvalds
2008-07-16 2:24 ` Tiago Assumpcao
2008-07-16 3:11 ` Theodore Tso
2008-07-16 9:49 ` pageexec
2008-07-16 10:08 ` David Miller
2008-07-16 10:23 ` pageexec
2008-07-16 10:31 ` David Miller
2008-07-16 10:51 ` pageexec
2008-07-16 11:04 ` David Miller
2008-07-16 11:52 ` pageexec
2008-07-16 3:13 ` Greg KH
2008-07-16 9:01 ` pageexec
2008-07-16 9:35 ` Gabor Gombas
2008-07-16 10:04 ` pageexec
2008-07-16 14:43 ` Greg KH
2008-07-16 15:43 ` pageexec
2008-07-16 16:29 ` Greg KH
2008-07-16 17:25 ` pageexec
2008-07-16 18:08 ` Theodore Tso
2008-07-16 19:09 ` pageexec
2008-07-17 3:43 ` Mike Galbraith
2008-07-16 1:08 ` Theodore Tso
2008-07-16 1:30 ` pageexec
2008-07-16 1:53 ` Tiago Assumpcao
2008-07-16 2:02 ` Linus Torvalds
2008-07-16 2:36 ` Tiago Assumpcao
2008-07-16 4:07 ` Linus Torvalds
2008-07-16 4:16 ` Tiago Assumpcao
2008-07-16 3:27 ` Casey Schaufler
2008-07-16 4:13 ` Tiago Assumpcao
2008-07-16 4:21 ` Linus Torvalds
2008-07-16 5:02 ` Tiago Assumpcao
2008-07-16 5:13 ` Linus Torvalds
2008-07-16 5:26 ` Casey Schaufler
2008-07-16 9:33 ` pageexec
2008-07-16 13:21 ` Theodore Tso
2008-07-16 15:16 ` pageexec
2008-07-16 0:04 ` pageexec
2008-07-16 0:24 ` Linus Torvalds
2008-07-16 0:56 ` pageexec
2008-07-16 1:08 ` Linus Torvalds
2008-07-16 1:23 ` pageexec
2008-07-17 7:19 ` Rafael C. de Almeida
2008-07-17 7:59 ` pageexec
2008-07-17 4:21 ` Phil Pell
2008-07-15 18:33 ` Theodore Tso
2008-07-15 20:28 ` pageexec
2008-07-15 22:39 ` Greg KH
2008-07-15 22:47 ` David Miller
2008-07-15 23:08 ` Tiago Assumpcao
2008-07-15 23:21 ` David Miller
2008-07-15 23:26 ` pageexec
2008-07-15 23:26 ` Tiago Assumpcao
2008-07-15 23:22 ` pageexec
2008-07-15 23:35 ` David Miller
2008-07-15 23:09 ` pageexec
2008-07-15 20:15 ` Tiago Assumpcao
2008-07-20 1:13 ` Bernd Eckenfels
2008-07-15 23:34 ` Tiago Assumpcao
2008-07-19 0:47 ` David Schwartz
2008-07-19 1:01 ` david [this message]
2008-07-19 1:51 ` David Schwartz
2008-07-19 5:41 ` Willy Tarreau
2008-07-05 7:54 ` Bart Van Assche
2008-07-08 4:12 ` 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=alpine.DEB.1.10.0807181755590.30465@asgard.lang.hm \
--to=david@lang.hm \
--cc=davids@webmaster.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/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
all inboxes | Powered by JetHome®