1 |
On Wed, May 10, 2017 at 01:44:06AM +0200, Andreas K. Huettel wrote: |
2 |
> Am Dienstag, 9. Mai 2017, 22:10:21 CEST schrieb Alexis Ballier: |
3 |
> > |
4 |
> > Do you realize that this breaks linking against about any static lib |
5 |
> > ever built before upgrading ? And I'm not even considering people |
6 |
> > toggling the flag. |
7 |
> |
8 |
> Toggling the flag is definitely bad. So it should be either on or off. |
9 |
> |
10 |
> > |
11 |
> > While I believe it might be a bit too early to default-enable pie, why |
12 |
> > not, but the news item *must* contain instructions that people should |
13 |
> > 'emerge -e world' in order for it to work. |
14 |
> > |
15 |
> > Also, I don't believe default-pie should even be a useflag. It's always |
16 |
> > been forced-on for hardened and forced-off for non-hardened I think. |
17 |
> > Switching between the two types of profiles has always been difficult |
18 |
> > because of that kind of differences. I strongly believe this should stay |
19 |
> > that way (that is: this cant be toggled by a simple useflag). |
20 |
> > |
21 |
> |
22 |
> Well... Hanno and Matthias said Gentoo is about the only place where it isn't |
23 |
> on by default. So why are we "early", and why not just force it on for |
24 |
> everybody? |
25 |
|
26 |
I just want to make sure im understanding this right, only .a files that |
27 |
were compiled without -pie will cause issues if you compile the later |
28 |
thing that uses the .a with -pie? |
29 |
So: |
30 |
1) people on hardened profiles are going to be fine no matter what? |
31 |
2) only packages that have .a files need to be rebuild? (not -e @world)? |
32 |
3) .a are static libs for compiling static binaries right, so nothing |
33 |
will break at runtime from the change? only build failures? |
34 |
|
35 |
I definitley think everyone on gentoo should have PIE and SSP by default |
36 |
nowadays. Whats the status of -zrelro -znow on non-hardened? |
37 |
|
38 |
This might be the kind of thing where a new set of profiles is a good |
39 |
idea |
40 |
1) hardened would force the flags on, |
41 |
2) 13.0 non-hardened would force them off |
42 |
3) 17.0 non-hardened would force them on and people have to rebuild when |
43 |
they change profiles |
44 |
|
45 |
Im not sure how the timing of the new profile would work? only make them |
46 |
once gcc-6 is stable so everyone does it at once? |
47 |
|
48 |
-- Jason |