public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The status of grsecurity upstream and hardened-sources downstream
Date: Fri, 23 Jun 2017 14:08:54 -0400	[thread overview]
Message-ID: <CAJ0EP43D4A3KWBnBpuft1G_vxz1c2A8gqoF4OGL9hawCRZ-p3w@mail.gmail.com> (raw)
In-Reply-To: <831a1b68-1083-ba04-faff-77267b7b06a1@gentoo.org>

On Fri, Jun 23, 2017 at 1:49 PM, Toralf Förster <toralf@gentoo.org> wrote:
> On 06/23/2017 06:28 PM, Anthony G. Basile wrote:
>>  I don't recommend we remove any of the machinery from Gentoo that deals with PaX
>> markings.
>
> I'm still using the hardened profile both at my desktop and my server -
> now together with latest stable vanilla-kernel by directly following the
> stable kernel git
> (echo "sys-kernel/vanilla-sources-4.10.13" >>
> /etc/portage/profile/package.provided).
> I realized (at the tinderbox images as well), that PAX-marking error
> messages do occur, when I didn't add '-paxkernel' to my USE flags.

The errors probably stem from lack of xattr support on tmpfs. Both
gentoo-sources and hardened-sources include a patch to enable this
(1500_XATTR_USER_PREFIX.patch).

You can either switch to gentoo-sources, or set PAX_MARKINGS="none" in
make.conf.


  reply	other threads:[~2017-06-23 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 16:28 [gentoo-project] The status of grsecurity upstream and hardened-sources downstream Anthony G. Basile
2017-06-23 17:27 ` William L. Thomson Jr.
2017-06-23 17:49 ` Toralf Förster
2017-06-23 18:08   ` Mike Gilbert [this message]
2017-06-23 18:47   ` Michael Orlitzky
2017-06-23 18:04 ` NP-Hardass
2017-06-23 18:54 ` Alice Ferrazzi
2017-06-23 20:46 ` Sergei Trofimovich

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=CAJ0EP43D4A3KWBnBpuft1G_vxz1c2A8gqoF4OGL9hawCRZ-p3w@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-project@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