1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 01/09/2014 05:21 PM, Michał Górny wrote: |
5 |
> Dnia 2014-01-09, o godz. 17:06:52 |
6 |
> "Anthony G. Basile" <blueness@g.o> napisał(a): |
7 |
> |
8 |
>> On 01/09/2014 04:57 PM, Pacho Ramos wrote: |
9 |
>>> What are the advantages of disabling SSP to deserve that "special" |
10 |
>>> handling via USE flag or easily disabling it appending the flag? |
11 |
>> |
12 |
>> There are some cases where ssp could break things. I know of once case |
13 |
>> right now, but its somewhat exotic. Also, sometimes we *want* to break |
14 |
>> things for testing. I'm thinking here of instance where we want to test |
15 |
>> a pax hardened kernel to see if it catches abuses of memory which would |
16 |
>> otherwise be caught by executables emitted from a hardened toolchain. |
17 |
>> Take a look at the app-admin/paxtest suite. |
18 |
> |
19 |
> Just to be clear, are we talking about potential system-wide breakage |
20 |
> or single, specific packages being broken by SSP? In other words, are |
21 |
> there cases when people will really want to disable SSP completely? |
22 |
> |
23 |
> Unless I'm misunderstanding something, your examples sound like you |
24 |
> just want -fno-stack-protector per-package. I don't really think you |
25 |
> actually want to rebuild whole gcc just to do some testing on a single |
26 |
> package... |
27 |
> |
28 |
Or just as easily set -fno-stack-protector in CFLAGS in make.conf. |
29 |
|
30 |
I never felt manipulating cflags with use flags was a great idea, but in |
31 |
this case is does feel extra pointless. |
32 |
|
33 |
Personally I don't feel this is needed, and the added benefit of |
34 |
clearing up a bogus "noblah" use flag makes me smile. |
35 |
|
36 |
Zorry, do we really need this flag? |
37 |
|
38 |
- -Zero |
39 |
-----BEGIN PGP SIGNATURE----- |
40 |
Version: GnuPG v2.0.22 (GNU/Linux) |
41 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
42 |
|
43 |
iQIcBAEBAgAGBQJSzyLGAAoJEKXdFCfdEflKo44QAJ4wYfgHdLYffTPaiXZe2ZJn |
44 |
3jPxaZX47m7BjgdtePZZncClby5h84cG+Jchb0pn/a6K6TknpiFXLQzArsJbMH0N |
45 |
th7cuuuS4iFQMw2xq8hNAvGAdMF4R0+/OSpBkzlskakcCVRHgV+KCz9llimny4hB |
46 |
RbTXK9Irva0bwYb5IkmTq+/JVqHjB5DyXUYMu32vdvgz8uxTPXXHHO5HtPlkLeiq |
47 |
YsumFhnHFb5d+yPvPzZ3YSMJyuHHtBeZFCOJoirtxL08+yr5dZhgppEbqkMJcHIG |
48 |
r1xKxPqFSmccHSJ8mCZ+l3mvrSL7Akd7D9c7Rk6hZ8RpMQnxCTNb3/Twq6oqAqKm |
49 |
JfcU1B6rKIDz6eZOtMmVMyVcfnlo7MHO/resmFCS/BYN5AyqyfHgn+I4OU4IVCvQ |
50 |
2jaZOwxeXGePgkwK37ebK/274N63lSkQAbaB0K43oqvsmtNuq+qZQQEm7jkY+0Vu |
51 |
SYKc3y4hXeLvexxteiR559fB7zJ1zPIsvvOWrqVP7euYezPMI7cjamz+7VHJYyH4 |
52 |
3RdGpro4Qg7OOTr42naBsWBW20nRTecWpm6kg0jyJo9eSD5YPzLq5r9ITcv7c6mB |
53 |
/6OxgqbVubzxpo9+kpY/11rEgQx5li4wKbLVsBY3n/f+tDCi1GNTu2k6ottdgrt2 |
54 |
XgsAKT4j/dUq8dhh80P7 |
55 |
=9pZW |
56 |
-----END PGP SIGNATURE----- |