1 |
>> glsa-check is working fine, it was a slotted issue. Still curious |
2 |
>> about a way to check for statically linked packages. |
3 |
> |
4 |
> There is no simple solution for this... USE flags static and |
5 |
> static-libs handle cases where there is a choice between static and |
6 |
> non-static version. In theory it is possible that some package |
7 |
> (like boot loader helper) can be linked only statically, thus you |
8 |
> will not be able to find it by USE flag. Though probability of this |
9 |
> is very low, and due to a special nature of such binaries (or |
10 |
> libraries) attack surface is even less. |
11 |
> |
12 |
> So you may assume your system reasonable secure if: |
13 |
> - all GLSAs are applied; |
14 |
> - there are no preserved libraries left (all packages using |
15 |
> vulnerable libs must be rebuilt); |
16 |
> - all static binaries and libraries depending directly or |
17 |
> indirectly on vulnerable packages are rebuild; |
18 |
> - there are no running processes using deleted files (reboot is a |
19 |
> brute, but effective way to do this, otherwise one should grep lsof |
20 |
> -n output for "(deleted)" files in use). |
21 |
|
22 |
|
23 |
I think 'checkrestart' is a good substitute for this. |
24 |
|
25 |
|
26 |
> - kernel should be updated to the latest version in branch if it is |
27 |
> still supported, or upgrade to another branch, preferably LTS, if |
28 |
> it is EOLed already. |
29 |
> |
30 |
> I have not seen GLSAs for kernel in ages, though old kernels |
31 |
> definitely have serious security issues, and they may be far more |
32 |
> serious than Ghost glibc bug. |
33 |
|
34 |
|
35 |
I didn't know that, thank you. |
36 |
|
37 |
- Grant |