Re: The state of grsecurity in gentoo
"Aaron W. Swenson" <[email protected]> Wed, 2 Sep 2015 13:22:22 -0400
| Newsgroups | gmane.linux.gentoo.hardened |
|---|---|
| Message-ID | <[email protected]> |
On 2015-09-02 12:13, Anthony G. Basile wrote: > Hi everyone, > > So by now most people have heard the news that the Grsecurity/PaX team > are no longer going to be making their stable patches available. The > reason is that they are in dispute with a certain embedded systems > vendor and those negotiations broke down. So they decided to make their > stable patches only available to the sponsors. [1] > > What does this mean for Gentoo? Up until now I have been maintaining > both the grsec upstream stable and testing patchsets in our > hardened-sources. Currently the upstream stable kernels are 3.2.71 and > 3.14.51 and the testing are 4.1.6. In about one week, the 3.2.71 and > 3.14.51 patchsets will no longer be available and I'll continue pushing > out the 4.1.6. Unfortunately the testing patchset is precisely as the > name suggests --- for testing and not production. For the embedded > systems company this will be the kiss of death because those patches are > not suitable for long term. For Gentoo it will mean that I will have to > be more vigilant about bugs and trying to stick with a well known kernel > before moving on. You can still use these kernels in production, but > you must be carefull about instabilities as upstream pushes out > experimental feature that may oops or panic. Keep older kernel images > around and revert if it doesn't work. Look to this list for > announcements about more serious issues like things that can cause data > loss. This would be a pretty good news item. Are you going to make it one?
signature.asc
(application/pgp-signature, 345 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0 iL4EAREKAGYFAlXnME5fFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDRGNEVENDM2QzYzRDAwQTdCNDYzQTQwMDI4 OTc2MzczNjFENjJENUQACgkQKJdjc2HWLV3f9QD9GRq0zCv9LT5rZ3bEHJjdkaiJ GB99LA+BeoBkD3MpfEUA/1CJanx2XlCajDFbcmQV2lQVnwiIfECmU7ZWPaEgxZot =sCpJ -----END PGP SIGNATURE-----