On 08/17/2012 04:19 PM, Tóth Attila wrote:
That is exactly what hardened sources package maintainers do.
There's always a tiny time difference between the latest grsecurity patch
showing up on the homepage and the respective kernel ebuild appears.
I try to get most of upstream's releases into
I recently moved my server from:
3.2.11-hardened
Security Level (Hardened Gentoo [server])
to:
3.4.5-hardened
Configuration Method (Automatic)
Usage Type (Server)
Virtualization Type (None)
Required Priorities (Security)
and http became extremely slow. Some pages that would normally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.08.2012 08:56, Grant wrote:
I recently moved my server from:
3.2.11-hardened Security Level (Hardened Gentoo [server])
to:
3.4.5-hardened Configuration Method (Automatic) Usage Type
(Server) Virtualization Type (None) Required
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.08.2012 11:47, Grant wrote:
I recently moved my server from:
3.2.11-hardened Security Level (Hardened Gentoo [server])
to:
3.4.5-hardened Configuration Method (Automatic) Usage Type
(Server) Virtualization Type (None) Required
I misread the part about the laptop. As far as I remember the only
supported versions by Upstream are 2.6.32.59 and 3.2.27 as stable and
3.5.2 as testing (the versions on grsecurity.net, right now).
Other versions aren't supported by upstream.
Interesting, I would have thought Gentoo would
El 17/08/12 19:06, Grant escribió:
Interesting, I would have thought Gentoo would keep hardened-sources
in sync with upstream's recommendation/support.
There are a few reasons for that not being the case but of them I'd go
for the fact that in order to get stabilished a package must have been
on
That is exactly what hardened sources package maintainers do.
There's always a tiny time difference between the latest grsecurity patch
showing up on the homepage and the respective kernel ebuild appears.
*hardened-sources-3.5.1-r2 (16 Aug 2012)
16 Aug 2012; Anthony G. Basile (blueness)
On Fri, Aug 17, 2012 at 11:19 PM, Tóth Attila at...@atoth.sote.hu wrote:
That is exactly what hardened sources package maintainers do.
There's always a tiny time difference between the latest grsecurity patch
showing up on the homepage and the respective kernel ebuild appears.
First, I would
