public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Francisco Blas Izquierdo Riera (klondike)" <klondike@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: pr@gentoo.org, gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-dev] New item for sys-kernel/hardened-sources removal
Date: Wed, 16 Aug 2017 12:09:57 +0200	[thread overview]
Message-ID: <bdc66209-8bb9-f645-9714-8d3116a85e8e@gentoo.org> (raw)
In-Reply-To: <9dfffef9-e2fc-dc97-6258-219de98e8b13@gentoo.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 835 bytes --]

El 16/08/17 a las 09:40, Marek Szuba escribió:
> Two tiny bits of formal nitpicking from my side:
>  - it's "grsecurity" (not a typo, they do use a lowercase g except when
> the name appears at the beginning of a sentence), not "grsec";
>  - the patches were not *distributed by* grsecurity, they *are*
> grsecurity. The vendor's name is Open Source Security, Inc.

Nowadays it is, but this hasn't always been the case. You'll notice the
presence of a /dev/grsec and you'll also find grsec referenced accross
some old patches. Anyways I changed it.

The same applies to Open Source Security, Inc. the company was founded
on 2008 but grsecurity has been around for much longer. That's why I
prefer to refer to Brad Spengler and The PaX team here as they are still
the real upstream behind Open Source Security, Inc.



[-- Attachment #1.1.2: 2017-08-19-hardened-sources-removal.en.txt --]
[-- Type: text/plain, Size: 2320 bytes --]

Title: sys-kernel/hardened-sources removal
Author: Francisco Blas Izquierdo Riera <klondike@gentoo.org>
Posted: 2017-08-19
Revision: 4
News-Item-Format: 2.0
Display-If-Installed: sys-kernel/hardened-sources
Display-If-Profile: hardened/linux/*

As you may know the core of sys-kernel/hardened-sources have been the
grsecuirty patches.

Sadly, their developers have stopped making these patches freely
available [1]. This is a full stop of any public updates and not only
stable ones as was announced two years ago[2].

As a result, the Gentoo Hardened team is unable to keep providing
further updates of the patches, and although the hardened-sources have
proved (when using a hardened toolchain) being resistant against
certain attacks like the stack guard page jump techniques proposed by
Stack Clash, we can't ensure a regular patching schedule and therefore,
the security of the users of these kernel sources.

Because of that we will be masking the hardened-sources on the 27th of
August and will proceed to remove them from the tree by the end of
September. Obviously, we will reinstate the package again if the
developers decide to make their patches publicly available again.

Our recommendation is that users should consider using instead
sys-kernel/gentoo-sources.

As an alternative, for users happy keeping themselves on the stable
4.9 branch of the kernel; minipli, another grsecurity user, is forward
porting the patches on [3].

Strcat from Copperhead OS is making his own version of the patches
forward ported to the latest version of the Linux tree at [4].

The Gentoo Hardened team can't make any statement regarding the
security, reliability or update availability of either those patches
as we aren't providing them and can't therefore make any
recommendation regarding their use.

We'd like to note that all the userspace hardening and MAC support
for SELinux provided by Gentoo Hardened will still remain there and
is unaffected by this removal. Also, all PaX related packages other
than the hardened-sources will remain for the time being.

[1] https://grsecurity.net/passing_the_baton.php
[2] https://www.gentoo.org/support/news-items/2015-10-21-future-support-of-
hardened-sources-kernel.html
[3] https://github.com/minipli/linux-unofficial_grsec
[4] https://github.com/copperhead/linux-hardened

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

  reply	other threads:[~2017-08-16 10:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 15:01 [gentoo-dev] New item for sys-kernel/hardened-sources removal Francisco Blas Izquierdo Riera (klondike)
2017-08-15 15:46 ` Francisco Blas Izquierdo Riera (klondike)
2017-08-15 16:08   ` Ulrich Mueller
2017-08-15 20:07     ` Francisco Blas Izquierdo Riera (klondike)
2017-08-15 15:50 ` R0b0t1
2017-08-15 20:03   ` Francisco Blas Izquierdo Riera (klondike)
2017-08-18  0:59     ` R0b0t1
2017-08-19 10:54       ` [gentoo-dev] About " Francisco Blas Izquierdo Riera (klondike)
2017-08-16  7:40 ` [gentoo-dev] New item for " Marek Szuba
2017-08-16 10:09   ` Francisco Blas Izquierdo Riera (klondike) [this message]
2017-08-16 16:01     ` Duncan
2017-08-17 22:54       ` Francisco Blas Izquierdo Riera (klondike)
2017-08-19 10:37 ` Aaron W. Swenson
2017-08-19 11:01   ` Francisco Blas Izquierdo Riera (klondike)
2017-08-19 11:18     ` Aaron W. Swenson
2017-08-19 11:34       ` Francisco Blas Izquierdo Riera (klondike)
2017-08-20  5:39         ` R0b0t1
2017-08-20  6:05           ` R0b0t1
2017-08-20  7:53           ` Michał Górny
2017-08-20  9:31             ` [gentoo-dev] " Duncan
2017-08-19 22:15       ` Duncan
2017-08-19 22:44         ` Michał Górny
2017-08-20 18:47           ` Francisco Blas Izquierdo Riera (klondike)

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=bdc66209-8bb9-f645-9714-8d3116a85e8e@gentoo.org \
    --to=klondike@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-hardened@lists.gentoo.org \
    --cc=pr@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