All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Schaufler, Casey" <casey.schaufler@intel.com>
To: "kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>
Subject: RE: [kernel-hardening] Project convention on configuration options
Date: Fri, 11 Dec 2015 21:09:41 +0000	[thread overview]
Message-ID: <99FC4B6EFCEFD44486C35F4C281DC6731F1E0062@ORSMSX107.amr.corp.intel.com> (raw)
In-Reply-To: <CAFwXZv8qbWA5V_v4M2ayZM5WA7rxyVn9SYLN6fGVuvMUDLfKwA@mail.gmail.com>

> -----Original Message-----
> From: HacKurx [mailto:hackurx@gmail.com]
> Sent: Friday, December 11, 2015 12:25 PM
> To: kernel-hardening@lists.openwall.com
> Subject: Re: [kernel-hardening] Project convention on configuration options
> 
> First, respect the work of others...
> https://twitter.com/ioerror/status/636677916365996032
> 
> So I hope you are not here for nothing...
> Sorry for such a comment here but I don't like attitude of your enterprise.

Noted.

So, on the topic at hand, what would you suggest? I see real
value in retaining as much of what's been proposed before as
possible.

> 
> 2015-12-11 18:57 GMT+01:00 Schaufler, Casey <casey.schaufler@intel.com>:
> >
> >
> > I’m starting to look at PAX_USERCOPY and immediately hit
> > the question of what to do about configuration option name.
> > I assume that retaining PAX_USERCOPY is not the right thing
> > to do, but what should be used instead? HARD_USERCOPY?
> >
> > Thanks.
> >
> >
> 
> --
> Best regards,

  parent reply	other threads:[~2015-12-11 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 17:57 [kernel-hardening] Project convention on configuration options Schaufler, Casey
2015-12-11 18:47 ` Kees Cook
2015-12-11 19:17   ` Daniel Micay
2015-12-11 20:24 ` HacKurx
2015-12-11 21:06   ` Kees Cook
2015-12-11 21:09   ` Schaufler, Casey [this message]
2015-12-11 21:48     ` HacKurx
2015-12-11 21:57       ` Kees Cook
2015-12-11 22:46         ` HacKurx
2015-12-11 22:59       ` Valdis.Kletnieks
2015-12-12  9:17         ` HacKurx
2015-12-13 16:36           ` Kees Cook

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=99FC4B6EFCEFD44486C35F4C281DC6731F1E0062@ORSMSX107.amr.corp.intel.com \
    --to=casey.schaufler@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.