public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] The status of grsecurity upstream and hardened-sources downstream
Date: Tue, 18 Jul 2017 09:37:29 -0500	[thread overview]
Message-ID: <CAAD4mYiiqS+ufy55G2SX3GpefvVy113KKeBCDr1h00H+FJrEyQ@mail.gmail.com> (raw)
In-Reply-To: <20170718103416.GF2178@home.power>

On Tue, Jul 18, 2017 at 5:34 AM, Alex Efros <powerman@powerman.name> wrote:
> Hi!
>
> On Fri, Jun 23, 2017 at 12:28:27PM -0400, Anthony G. Basile wrote:
>> My plan then is as follows.  I'll wait one more month and then send out
>> a news item and later mask hardened-sources for removal.
>
> Well, it's about a month now. I didn't replied earlier because others
> already mentioned all good ideas and I was hoping these ideas will be
> accepted… :(
>
> But, just in case, I'm +1 for both ideas to keep 4.9 LTS support as long
> as possible (and mark one of hardened-sources-4.9.x as stable) to give us
> a couple of years [...]
>

I agree, there are this solution seems popular among people using
other distributions who want to continue to use grsecurity.


  reply	other threads:[~2017-07-18 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 16:28 [gentoo-hardened] The status of grsecurity upstream and hardened-sources downstream Anthony G. Basile
2017-06-23 17:01 ` Oleg Popov
2017-06-23 17:09 ` Javier Juan Martinez Cabezon
2017-07-24 16:46   ` Cor Legemaat
2017-07-24 17:02     ` Javier Juan Martinez Cabezon
2017-07-26  1:48     ` Jens Kasten
2017-06-23 17:47 ` Kevin Chadwick
2017-06-23 20:46 ` [gentoo-hardened] Re: [gentoo-project] " Sergei Trofimovich
2017-06-24 10:59 ` [gentoo-hardened] " Francisco Blas Izquierdo Riera (klondike)
2017-07-18 10:34 ` Alex Efros
2017-07-18 14:37   ` R0b0t1 [this message]
2017-07-18 14:39     ` R0b0t1

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=CAAD4mYiiqS+ufy55G2SX3GpefvVy113KKeBCDr1h00H+FJrEyQ@mail.gmail.com \
    --to=r030t1@gmail.com \
    --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