From: Doug McNaught <doug@wireboard.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] prevention of syscalls from writable segments, breaking bug exploits
Date: 03 Jan 2001 17:10:43 -0500 [thread overview]
Message-ID: <m34rzgl21o.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0101031406160.31664-100000@anime.net>
In-Reply-To: Dan Hollis's message of "Wed, 3 Jan 2001 14:07:14 -0800 (PST)"
Dan Hollis <goemon@anime.net> writes:
> On Wed, 3 Jan 2001, Alexander Viro wrote:
> > On Wed, 3 Jan 2001, Dan Aloni wrote:
> > > without breaking anything. It also reports of such calls by using printk.
> > Get real.
>
> Why do you always have to be insulting alex? Sheesh.
I was thinking it's about time this flamewar^Wthread came up again.
Shall we start a pool on total # of messages, first invocation of
Godwin's law, etc?
-Doug
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-03 22:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 21:13 [RFC] prevention of syscalls from writable segments, breaking bug exploits Dan Aloni
2001-01-03 21:36 ` Dan Aloni
2001-01-03 21:48 ` [RFC] prevention of syscalls from writable segments, breaking bugexploits Brian Gerst
2001-01-03 21:54 ` [RFC] prevention of syscalls from writable segments, breaking bug exploits Alexander Viro
2001-01-03 22:03 ` Dan Aloni
2001-01-03 22:13 ` Alexander Viro
2001-01-03 22:05 ` Steven Walter
2001-01-03 22:07 ` Dan Hollis
2001-01-03 22:10 ` Doug McNaught [this message]
2001-01-03 22:31 ` Alexander Viro
2001-01-03 22:39 ` Mark Zealey
2001-01-03 22:49 ` Alexander Viro
2001-01-03 22:55 ` Mark Zealey
2001-01-03 22:48 ` Dan Aloni
2001-01-03 23:02 ` Alexander Viro
2001-01-03 23:32 ` Dan Hollis
2001-01-03 23:48 ` Nicolas Noble
2001-01-03 23:54 ` Gerhard Mack
2001-01-03 23:57 ` Dan Hollis
2001-01-04 0:34 ` Gerhard Mack
2001-01-04 1:01 ` Dan Hollis
2001-01-04 7:09 ` Gerhard Mack
2001-01-03 23:34 ` Gerhard Mack
2001-01-04 1:51 ` Andi Kleen
2001-01-03 21:57 ` Erik Mouw
2001-01-03 22:12 ` Nicolas Noble
2001-01-03 22:30 ` Pavel Machek
2001-01-03 23:02 ` [RFC] prevention of syscalls from writable segments, breaking bug Alan Cox
2001-01-05 15:26 ` 2.2.19pre6 maestro3 driver requires ac97_codec (but doesn't claim so) Richard A Nelson
2001-01-03 23:20 ` [RFC] prevention of syscalls from writable segments, breaking bug exploits Jeff Dike
2001-01-04 3:20 ` David Huggins-Daines
2001-01-04 3:32 ` Andi Kleen
2001-01-04 3:41 ` David Huggins-Daines
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=m34rzgl21o.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=linux-kernel@vger.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