public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] overview of PaX features
Date: Wed, 29 Jun 2011 22:25:05 +0400	[thread overview]
Message-ID: <20110629182505.GC14873@openwall.com> (raw)
In-Reply-To: <20110626183321.GA3867@albatros>

Vasiliy,

On Sun, Jun 26, 2011 at 10:33:21PM +0400, Vasiliy Kulikov wrote:
> PaXTeam said there is almost nothing I can do with userspace NX.
> Currently it is implemented as a "stack can be X unless GNU_STACK is
> enabled" instead of secure by default policy.  It's impossible to fix it
> not breaking the compatibility with old apps.  So, I'm skipping NOEXEC
> options.

Please do break compatibility with a handful of old apps - but as a
non-default option (which we're likely to make the default on Owl, just
like we had non-executable stack by default with 2.4.x-ow kernels).

With OpenVZ, it needs to be configurable per-container.

This is an important security hardening feature for us to have, so
please proceed to implement it sooner rather than later.

I'm sorry that I haven't reviewed the rest of your message yet (and am
in fact a bit late with this comment as well...)

Thanks,

Alexander

  reply	other threads:[~2011-06-29 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26 18:33 [kernel-hardening] overview of PaX features Vasiliy Kulikov
2011-06-29 18:25 ` Solar Designer [this message]
2011-06-29 18:37   ` Vasiliy Kulikov
2011-06-29 19:43     ` Solar Designer
2011-06-30 16:03       ` Vasiliy Kulikov
2011-07-02 17:21         ` Solar Designer
2011-07-02 17:46           ` Vasiliy Kulikov
2011-07-03  1:06       ` Anthony G. Basile

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=20110629182505.GC14873@openwall.com \
    --to=solar@openwall.com \
    --cc=kernel-hardening@lists.openwall.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