From: ebiederm@xmission.com (Eric W. Biederman)
To: John Levon <movement@marcelothewonderpenguin.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Steven N. Hirsch" <shirsch@adelphia.net>,
linux-kernel@vger.kernel.org
Subject: Re: Two fixes for 2.4.19-pre5-ac3
Date: 07 Apr 2002 14:10:42 -0600 [thread overview]
Message-ID: <m1y9fzmfr1.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20020407173343.GA18940@compsoc.man.ac.uk> <E16uIf7-0006Zw-00@the-village.bc.nu> <20020407194114.GA21800@compsoc.man.ac.uk>
John Levon <movement@marcelothewonderpenguin.com> writes:
> On Sun, Apr 07, 2002 at 08:49:17PM +0100, Alan Cox wrote:
>
> > Removing it in the -ac tree is a good way to stimulate discussion
>
> OK
>
> > fixing the code that relies on it (except for the 99% of code relying on it
> > which is cracker authored trojans)
>
> No doubt, but it's not much harder to look at nm vmlinux or System.map,
> so I don't see the security angle...
>
> I'd be happy to bear the brunt of users moaning at me because they now
> have to apply a kernel patch (and I have to maintain it ...), iff there
> was some strongly technical reason the code has to change.
Deep technical reason there are architectures where patching the
system call table does not work.
Eric
next prev parent reply other threads:[~2002-04-07 20:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 16:43 Two fixes for 2.4.19-pre5-ac3 Steven N. Hirsch
2002-04-07 17:11 ` Christoph Hellwig
2002-04-07 17:14 ` arjan
2002-04-07 17:42 ` Alan Cox
2002-04-07 17:27 ` arjan
2002-04-07 17:48 ` Alexander Viro
2002-04-07 17:33 ` John Levon
2002-04-07 19:18 ` Alan Cox
2002-04-07 19:23 ` John Levon
2002-04-07 19:42 ` Alan Cox
2002-04-07 19:32 ` John Levon
2002-04-07 19:58 ` Alan Cox
2002-04-07 19:40 ` Jan Harkes
2002-04-07 20:01 ` Alan Cox
2002-04-07 20:13 ` Jan Harkes
2002-04-07 19:49 ` Alan Cox
2002-04-07 19:41 ` John Levon
2002-04-07 19:55 ` Muli Ben-Yehuda
2002-04-07 20:29 ` Alan Cox
2002-04-07 20:23 ` Muli Ben-Yehuda
2002-04-07 20:51 ` Alan Cox
2002-04-07 23:03 ` Anton Altaparmakov
2002-04-08 6:27 ` Muli Ben-Yehuda
2002-04-07 20:02 ` Alan Cox
2002-04-07 20:10 ` Eric W. Biederman [this message]
2002-04-07 23:06 ` John Levon
2002-04-07 19:44 ` Steven N. Hirsch
2002-04-08 14:48 ` Bill Davidsen
2002-04-08 16:06 ` Philippe Elie
2002-04-08 17:53 ` Eric W. Biederman
2002-04-08 18:07 ` John Levon
2002-04-07 23:31 ` Erik Tews
[not found] <20020407193245.GA21570@compsoc.man.ac.uk.suse.lists.linux.kernel>
[not found] ` <E16uIoN-0006b3-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-04-07 21:34 ` Andi Kleen
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=m1y9fzmfr1.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=movement@marcelothewonderpenguin.com \
--cc=shirsch@adelphia.net \
/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