Gentoo Archives: gentoo-security

From: aeonflux <aeonflux@××××××××××××××.com>
To: Stephen Clowater <steve@×××××××××××××××××.org>
Cc: gentoo-security@l.g.o
Subject: Re: [gentoo-security] grSecurity Information
Date: Thu, 19 Feb 2004 05:28:13
Message-Id: 40344961.4010707@aeonflux.no-ip.com
In Reply to: Re: [gentoo-security] grSecurity Information by Stephen Clowater
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Stephen Clowater wrote:
5 | Compiling from stage 1 is a very important step, by compiling everythig,
6 | and by turning on the memory randomization features in GRsecurity
7 | (random mallac() base as a _very_ good one that I sorly miss on 2.6.0 as
8 | I wait like a 18 year old girl on prom night for the 2.6.0 GRsecurity
9 | patch :)) you will do alot to protect yourself.
10 Actually that's wrong. The system call is changed in the kernel, so
11 regardless of whether or not the program was compiled/linked before or
12 after it will have the same effect. malloc() will return an integer
13 that's more random then before.
14
15 You could put grsecurity kernel on a stock redhat box, and still benefit
16 as much as recompiling everything from scratch.
17
18 -----BEGIN PGP SIGNATURE-----
19 Version: GnuPG v1.2.1 (MingW32)
20
21 iD8DBQFANElX1mDajpZ9rHwRAtJIAJ9tgFopsjGTfSyjQOjimFjKpbmWIwCg2tDh
22 K7zzKhtwY196GoeIf+gzJKg=
23 =MUrP
24 -----END PGP SIGNATURE-----
25
26 --
27 gentoo-security@g.o mailing list