From: Stefanos Harhalakis <v13@priest.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Robert White <rwhite@casabyte.com>,
"'Ingo Molnar'" <mingo@elte.hu>,
"'Christoph Hellwig'" <hch@infradead.org>,
"'Mike McCormack'" <mike@codeweavers.com>,
linux-kernel@vger.kernel.org
Subject: Re: WINE + NX (No eXecute) support for x86, 2.6.7-rc2-bk2
Date: Thu, 10 Jun 2004 21:07:47 +0300 [thread overview]
Message-ID: <200406102107.53776.v13@priest.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0406091911340.26677@jjulnx.backbone.dif.dk>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On Wednesday 09 June 2004 20:14, Jesper Juhl wrote:
> On Tue, 8 Jun 2004, Robert White wrote:
> > I would think that having an easy call to disable the NX modification
> > would be both safe and effective. That is, adding a syscall (or
> > whatever) that would let you mark your heap and/or stack executable while
> > leaving the new default as NX, is "just as safe" as flagging the
> > executable in the first place.
>
> Just having the abillity to turn protection off opens the door. If it is
> possible to turn it off then a way will be found to do it - either via
> buggy kernel code or otherwhise. Only safe approach is to have it
> enabled by default and not be able to turn it off IMHO.
What about turning it on and don't be able to turn it off again?
> Jesper Juhl <juhl-lkml@dif.dk>
<<V13>>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-10 18:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 6:09 WINE + NX (No eXecute) support for x86, 2.6.7-rc2-bk2 Mike McCormack
2004-06-06 5:26 ` Ingo Molnar
2004-06-06 8:29 ` Mike McCormack
2004-06-06 7:32 ` Arjan van de Ven
2004-06-08 9:20 ` Jakub Jelinek
2004-06-08 11:15 ` Mike McCormack
2004-06-08 10:32 ` Ingo Molnar
2004-06-08 12:01 ` Mike McCormack
2004-06-09 1:40 ` John Reiser
2004-06-09 2:27 ` Paul Jackson
2004-06-06 7:32 ` Christoph Hellwig
2004-06-06 9:13 ` Mike McCormack
2004-06-06 8:10 ` Christoph Hellwig
2004-06-06 9:37 ` Mike McCormack
2004-06-06 8:39 ` Christoph Hellwig
2004-06-06 8:43 ` Christoph Hellwig
2004-06-06 10:20 ` Mike McCormack
2004-06-06 11:17 ` Felipe Alfaro Solana
2004-06-07 4:20 ` Horst von Brand
2004-06-07 14:19 ` Ingo Molnar
2004-06-08 21:50 ` Robert White
2004-06-08 21:57 ` Robert White
2004-06-09 16:53 ` Jesse Pollard
2004-06-09 20:53 ` Robert White
2004-06-10 13:35 ` Jesse Pollard
2004-06-10 21:13 ` Robert White
2004-06-11 9:50 ` Marc Bevand
2004-06-09 17:14 ` Jesper Juhl
2004-06-09 18:02 ` Evaldo Gardenali
2004-06-09 19:58 ` Felipe Alfaro Solana
2004-06-10 18:07 ` Stefanos Harhalakis [this message]
2004-06-06 11:38 ` David Woodhouse
2004-06-06 15:58 ` Mike McCormack
2004-06-07 8:49 ` David Howells
[not found] <23Y4Y-6F5-1@gated-at.bofh.it>
[not found] ` <240qb-8ir-7@gated-at.bofh.it>
[not found] ` <240Tc-gV-5@gated-at.bofh.it>
[not found] ` <2412S-pU-3@gated-at.bofh.it>
[not found] ` <24vX0-81P-7@gated-at.bofh.it>
2004-06-07 17:40 ` Andi Kleen
2004-06-08 9:42 ` Eric W. Biederman
[not found] ` <24WNz-4pO-3@gated-at.bofh.it>
2004-06-10 18:57 ` Bill Davidsen
2004-06-10 21:33 ` Robert White
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=200406102107.53776.v13@priest.com \
--to=v13@priest.com \
--cc=hch@infradead.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@codeweavers.com \
--cc=mingo@elte.hu \
--cc=rwhite@casabyte.com \
/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