1 |
Going to try to settle and clarify things once and for all. |
2 |
|
3 |
You can switch back to non hardened if needed, make sure you have your |
4 |
old non hardened kernel as an option on your bootloader just in case as |
5 |
that will disable most hardening features (including PIE), so your |
6 |
system will only have SSP as source of possible troubles. |
7 |
|
8 |
The steps on the FAQ have been agreeded by the whole hardened team on |
9 |
meetings, and there are reasons for them: |
10 |
You need to emerge gcc and glibc on the first stage to make sure they |
11 |
include any hardening needed since they are patched (at least gcc is and |
12 |
glibc includes the SSP code). |
13 |
You need to emerge then system for two reasons, first because if |
14 |
something fails going back will be easier, then because some of the |
15 |
system libraries and tools have hardening patches. |
16 |
Finally you need to emerge the whole world to make sure all the packages |
17 |
(even system ones) are built and linked with hardened features and |
18 |
libraries. |
19 |
In a similar way you can repeat the above steps again after going back |
20 |
to your preferred non hardened profile. |
21 |
Also remind that any changes from hardened to non hardened and viceversa |
22 |
must be made on a non hardened kernel. |
23 |
|
24 |
Tip: generate binary packages for world before jumping to hardened as |
25 |
that will make recovery easier in case the change fails and will speed |
26 |
up going back a lot. |
27 |
|
28 |
BTW: for those of you who haven't noticed we added the --keep-going flag |
29 |
to the system and world emerges so the system keeps trying to build if |
30 |
any of the packages fails, in that case filling a bug would be a good idea. |
31 |
|
32 |
Not more to say, if you need to run in softmode just follow the FAQ but |
33 |
then PaX will be mostly disabled so it is an almost not hardened kernel |
34 |
meanwhile. |