1 |
On Monday 24 November 2008 21:53:37 atoth@××××××××××.hu wrote: |
2 |
> Dear Jan, |
3 |
> |
4 |
> I've run through what I'd wrote and I have a feeling, that it can be |
5 |
> misleading. |
6 |
> So here is an actual example output of the command "gcc-config -l": |
7 |
> " |
8 |
> hostname ~ # gcc-config -l |
9 |
> [1] i686-pc-linux-gnu-4.2.4 * |
10 |
> [2] i686-pc-linux-gnu-4.2.4-nofortify |
11 |
> [3] i686-pc-linux-gnu-4.2.4-nopie |
12 |
> [4] i686-pc-linux-gnu-4.2.4-nossp_all |
13 |
> [5] i686-pc-linux-gnu-4.2.4-strict |
14 |
> [6] i686-pc-linux-gnu-4.2.4-vanilla |
15 |
> " |
16 |
> Here you can see, that the same version of gcc has several profiles. The |
17 |
> one without any additional tag is the default hardened profile. Compiles |
18 |
> hardened executables by default. The vanilla profile is intended to |
19 |
> implement the original non-hardened behavior. |
20 |
> I'm running the experimental hardened toolchain, which is the reason I |
21 |
> have entries 2, 4 and 5. If you are not using the experimental hardened |
22 |
> toolchain you should probably have to have 3.4.6, -nopie, -nossp and |
23 |
> -vanilla. If you have gcc-4+ and you are not using the experimental |
24 |
> hardened toolchain you are probably missing hardened toolchain features |
25 |
> (some developers tend to neglect and/or treat useless - I don't understand |
26 |
> why). |
27 |
> |
28 |
> Regards, |
29 |
> Dw. |
30 |
|
31 |
You are helpful this evening :) |
32 |
Well, I am reading about various things *hardened. |
33 |
|
34 |
Regards |