1 |
On Wed, 2004-09-22 at 11:54, John Richard Moser wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> It may be prudent to use extra protection on certain ebuilds in standard |
6 |
> Gentoo profiles where the changes would be significant in the case of a |
7 |
> security fault in the program. Such programs as daemons and chmod()+s |
8 |
> programs would be major targets for this sort of thing. |
9 |
> |
10 |
> The most immediately apparent route to take would be to have ebuilds |
11 |
> such as openssh, apache, and su stack smash protected. This would |
12 |
> prevent common buffer overflow attacks from being used to compromise |
13 |
> security; such attacks would only cause the program attacked to abort, |
14 |
> which could still be used as a Denial of Service attack, but would not |
15 |
> allow successful intrusion. |
16 |
> |
17 |
> Gentoo ships gcc with stack smash protection built in. This is |
18 |
> activated by -fstack-protector or -fstack-protector-all. It would be |
19 |
> feasible to add one of these flags to an ebuild based on a FEATURES or |
20 |
> USE setting. |
21 |
> |
22 |
> I believe it would be a good idea to have such a FEATURES or USE flag on |
23 |
> by default in all profiles where SSP is supported. In this manner, the |
24 |
> major targets of security attacks would automatically be protected; |
25 |
> while still allowing the user to disable the protection if the user |
26 |
> desires. Users wanting more protection can simply add -fstack-protector |
27 |
> to CFLAGS, or use Hardened Gentoo. |
28 |
> |
29 |
> Any comments? Would this be more suitable as a USE or a FEATURES setting? |
30 |
|
31 |
|
32 |
This would indeed significantly reduce impact of many existing security |
33 |
problems that could potentially introduce and execute arbitrary code. |
34 |
|
35 |
Yes this makes complete and total sense in the terms of what your saying |
36 |
here. Vs using hardened which is not ideal for everybody or all |
37 |
occasions(due to the other things it enables by default) to limit the |
38 |
use of -fstack-protector to/for setuid/setgid and services only. |
39 |
|
40 |
I fully support this idea for atleast all base system packages that fall |
41 |
under the conditions you have defined, and assuming to many trolls don't |
42 |
come out of the woodwork I would be willing start on it if you can make |
43 |
a detailed list. |
44 |
|
45 |
As far as a disable feature how about FEATURES="noautossp" ? |
46 |
|
47 |
> |
48 |
> - -- |
49 |
> All content of all messages exchanged herein are left in the |
50 |
> Public Domain, unless otherwise explicitly stated. |
51 |
> |
52 |
> -----BEGIN PGP SIGNATURE----- |
53 |
> Version: GnuPG v1.2.6 (GNU/Linux) |
54 |
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
55 |
> |
56 |
> iD8DBQFBUaBOhDd4aOud5P8RAv/sAKCGx+cy5D3U35jDvGEFV5fcInF2fwCfbvGM |
57 |
> QvF8iaV8fuNFVQcintwy+2o= |
58 |
> =4Gdc |
59 |
> -----END PGP SIGNATURE----- |
60 |
> |
61 |
> -- |
62 |
> gentoo-dev@g.o mailing list |
63 |
-- |
64 |
Ned Ludd <solar@g.o> |
65 |
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |