From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chase Venters <chase.venters@clientec.com>
Cc: Julio Auto <mindvortex@gmail.com>,
goodfellas@shellcode.com.ar,
Linux kernel <linux-kernel@vger.kernel.org>,
Kyle Moffett <mrmacman_g4@mac.com>,
endrazine <endrazine@gmail.com>,
Stephen Hemminger <shemminger@osdl.org>,
Valdis.Kletnieks@vt.edu
Subject: Re: Registration Weakness in Linux Kernel's Binary formats
Date: Wed, 04 Oct 2006 15:55:41 +0100 [thread overview]
Message-ID: <1159973741.25772.45.camel@localhost.localdomain> (raw)
In-Reply-To: <200610032326.10710.chase.venters@clientec.com>
Ar Maw, 2006-10-03 am 23:25 -0500, ysgrifennodd Chase Venters:
> I think it's a little bit silly for a "security researcher" to simultaneously
> publish stuff in the news and in a developer community, especially if the
> threat is totally phony to begin with.
Given the way it was carefully fed to slashdot I suspect it may in fact
be someone with brains who wanted to make slashdot look stupid and spoof
them. If so they certainly scored 10/10 on that.
next prev parent reply other threads:[~2006-10-04 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 4:08 Registration Weakness in Linux Kernel's Binary formats Julio Auto
2006-10-04 4:25 ` Chase Venters
2006-10-04 14:55 ` Alan Cox [this message]
2006-10-04 14:34 ` Xavier Bestel
2006-10-04 5:40 ` Kyle Moffett
2006-10-04 7:11 ` Peter Read
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 21:25 Fwd: " Bráulio Oliveira
2006-10-03 21:53 ` Kyle Moffett
2006-10-03 21:59 ` Stephen Hemminger
2006-10-03 22:28 ` Valdis.Kletnieks
2006-10-03 19:13 SHELLCODE Security Research
2006-10-03 21:48 ` Chase Venters
2006-10-03 22:54 ` Alan Cox
2006-10-04 3:49 ` Chase Venters
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=1159973741.25772.45.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=chase.venters@clientec.com \
--cc=endrazine@gmail.com \
--cc=goodfellas@shellcode.com.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=mindvortex@gmail.com \
--cc=mrmacman_g4@mac.com \
--cc=shemminger@osdl.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