From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The status of grsecurity upstream and hardened-sources downstream
Date: Fri, 23 Jun 2017 13:27:31 -0400 [thread overview]
Message-ID: <assp.0347b27f40.20170623132731.530e18ee@o-sinc.com> (raw)
In-Reply-To: <ea98b420-db01-4b70-68a3-f8f9a3f8b9cf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Fri, 23 Jun 2017 12:28:27 -0400
"Anthony G. Basile" <blueness@gentoo.org> wrote:
>
> I waited two months before saying anything because the reasons were
> more of a political nature than some technical issue. At this point,
> I think its time to let the community know about the state of affairs
> with hardened-sources.
Political is not really the correct terminology, more breach of
trademark. This was a business decision, I do not blame them!
https://grsecurity.net/announce.php
https://www.theregister.co.uk/2017/04/26/grsecurity_linux_kernel_freeloaders/
They are still available just not for free, for $200
https://grsecurity.net/purchase.php
Thanks WindRiver/Intel....
https://www.windriver.com/products/linux/security/
https://en.wikipedia.org/wiki/Wind_River_Systems
https://en.wikipedia.org/wiki/Wind_River_Systems#Wind_River_Linux
--
William L. Thomson Jr.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-06-23 17:27 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. [this message]
2017-06-23 17:49 ` Toralf Förster
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=assp.0347b27f40.20170623132731.530e18ee@o-sinc.com \
--to=wlt-ml@o-sinc.com \
--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