public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luis Ressel <aranea@aixah.de>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Technical repercussions of grsecurity removal
Date: Mon, 8 May 2017 20:57:16 +0200	[thread overview]
Message-ID: <20170508205716.0d765a87@gentp.lnet> (raw)
In-Reply-To: <20170508180807.GA18570@g0n.xdwgrp>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

Hi,

I don't have much to add, but I'd like to clear two misunderstandings
here:

On Mon, 8 May 2017 20:08:07 +0200
Miroslav Rovis <miro.rovis@croatiafidelis.hr> wrote:

> And really since late in 2016 no more entries in the Changelog. Pls.
> note that I'm only stating the facts, not complaining.

AFAIK the Changelogs aren't updated anymore (in the whole gentoo tree).

> > * NSA SELinux instead PAX MPROTECT?  
> I hope this is a joke. It looks like one, at first sight, but there
> are half a dozen "NSA SELinux" instances to be found in the latest
> hardened-sources.
> 
> # grep 'NSA SE' /usr/src/linux/security/selinux/Kconfig 
> 	bool "NSA SELinux Support"
> 	...
> #
> (where linux is a hardened-sources installation)
> 
> If hardened would be down to SELinux, I wouldn't be hardening any
> more.

SELinux isn't a patch applied by hardened-sources, it's a subsystem of
the mainline kernel. grsec was really the only significant difference
between hardened-sources and gentoo-sources.

Regards,
Luis

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

  reply	other threads:[~2017-05-08 18:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01  9:38 [gentoo-hardened] Technical repercussions of grsecurity removal Sven Vermeulen
2017-05-01  9:50 ` Sven Vermeulen
2017-05-01 10:24 ` Daniel Cegiełka
2017-05-01 11:00   ` Andrew Savchenko
2017-05-01 12:25     ` Daniel Cegiełka
2017-05-01 10:28 ` Andrew Savchenko
2017-05-01 13:58   ` Sven Vermeulen
2017-05-01 14:20     ` SK
2017-05-01 14:53       ` Daniel Cegiełka
2017-05-01 15:21         ` SK
2017-05-02  8:28           ` Daniel Cegiełka
2017-05-08 18:08             ` Miroslav Rovis
2017-05-08 18:57               ` Luis Ressel [this message]
2017-05-08 20:07               ` Mathias Krause
2017-05-08 20:49                 ` Miroslav Rovis
2017-05-08 23:31                   ` Miroslav Rovis
2017-05-09 14:28                     ` [gentoo-hardened] Unofficial grsec kernel install WAS: " Miroslav Rovis
2017-05-08 21:12     ` [gentoo-hardened] " Andrew Savchenko
2017-05-12 19:10       ` "Tóth Attila"
2017-05-12 23:38         ` Alex Efros
2017-05-13  0:17           ` Max R.D. Parmer
2017-05-02 15:28 ` Luis Ressel
2017-05-02 15:56   ` Daniel Cegiełka
2017-05-02 16:02     ` Luis Ressel
2017-05-02 16:59       ` Daniel Cegiełka
2017-05-02 17:23         ` "Tóth Attila"
2017-05-02 19:58           ` Daniel Cegiełka
2017-05-02 20:41             ` Alex Efros

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=20170508205716.0d765a87@gentp.lnet \
    --to=aranea@aixah.de \
    --cc=gentoo-hardened@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