public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf@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 19:49:11 +0200	[thread overview]
Message-ID: <831a1b68-1083-ba04-faff-77267b7b06a1@gentoo.org> (raw)
In-Reply-To: <ea98b420-db01-4b70-68a3-f8f9a3f8b9cf@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 708 bytes --]

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.

I do wonder, if the PAX marking logic could detect a running
non-hardened kernel and therefore silently skip the step ?

-- 
Toralf
PGP 23217DA7 9B888F45



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2017-06-23 17:49 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 [this message]
2017-06-23 18:08   ` Mike Gilbert
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=831a1b68-1083-ba04-faff-77267b7b06a1@gentoo.org \
    --to=toralf@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