public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick McLean <chutzpah@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "Anthony G. Basile" <blueness@gentoo.org>
Subject: Re: [gentoo-dev] Regarding the State of PaX in the tree
Date: Mon, 16 Apr 2018 10:11:57 -0700	[thread overview]
Message-ID: <92a08276-d252-b028-8218-fbf8cb81b4a2@gentoo.org> (raw)
In-Reply-To: <0c21ceac-ed4f-4280-c46f-8a9b41641422@gentoo.org>

On 2018-04-16 05:12 AM, Anthony G. Basile wrote:
> On 4/16/18 4:05 AM, Marc Schiffbauer wrote:
>> * Anthony G. Basile schrieb am 16.04.18 um 02:04 Uhr:
>>> Hi everyone,
>>
>> Hi Anthony,
>>
>> I vote for keeping PaX Support as I am still using it and might be doing 
>> so in the future.
>>
>> Thanks ;)
>> -Marc
>>
> 
> How are you able to test?  Do you have your hands on the latest grsec
> patches or are you using an old kernel.  Old at this point means one
> year old.
> 

I am able to test, we have access to the latest grsecurity kernels at my
employer, and we would very much prefer to keep the PaX markings around.

We (I work with several Gentoo developers) are actively testing all the
packages we use internally with newer kernels, and fixing anything that
breaks.


  reply	other threads:[~2018-04-16 17:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  0:04 [gentoo-dev] Regarding the State of PaX in the tree Anthony G. Basile
2018-04-16  1:25 ` R0b0t1
2018-04-16  2:25 ` Sam Jorna
2018-04-16  6:06 ` Michał Górny
2018-04-16  7:22   ` Ulrich Mueller
2018-04-16 12:20     ` Anthony G. Basile
2018-04-16  8:05 ` Marc Schiffbauer
2018-04-16 12:12   ` Anthony G. Basile
2018-04-16 17:11     ` Patrick McLean [this message]
2018-04-19 12:05     ` Marc Schiffbauer
2018-04-16  9:14 ` Hanno Böck
2018-04-16 12:31   ` Anthony G. Basile
2018-04-16 14:26     ` Francesco Riosa
2018-04-16 17:53   ` Toralf Förster
2018-04-16 18:16     ` Jason Zaman

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=92a08276-d252-b028-8218-fbf8cb81b4a2@gentoo.org \
    --to=chutzpah@gentoo.org \
    --cc=blueness@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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