| 1 |
Hi! |
| 2 |
|
| 3 |
On Sun, Dec 11, 2011 at 10:18:51AM +0000, Sven Vermeulen wrote: |
| 4 |
> Also consider hardening your system settings-wise. I would appreciate if you |
| 5 |
> take a look at |
| 6 |
> http://dev.gentoo.org/~swift/docs/previews/oval/gentoo-xccdf-guide.html. |
| 7 |
|
| 8 |
Some points at that guide looks strange to me. For example: |
| 9 |
|
| 10 |
1) How can |
| 11 |
4.2.4.1. Root Logon Through SSH Is Not Allowed |
| 12 |
increase security, if we're already using |
| 13 |
4.2.4.2. Public Key Authentication Only |
| 14 |
Disabling root may have sense with password auth, but with keys it is |
| 15 |
just useless inconvenience. |
| 16 |
|
| 17 |
2) How can |
| 18 |
4.2.4.6. Listen on Management Interface |
| 19 |
increase security? Moreover, on multihomed systems listening on all |
| 20 |
interfaces may help you a lot in case one of network link is broken. |
| 21 |
|
| 22 |
3) In my experience, the |
| 23 |
4.4.2.2. Enable Source Route Verification |
| 24 |
often conflict with net-misc/openvpn based VPN interfaces. I didn't |
| 25 |
investigated this issue in deep, just google for issue and found |
| 26 |
solution which was to disable source route verification, and it works. |
| 27 |
Maybe there is exists better way to solve this issue, not sure. |
| 28 |
|
| 29 |
4) Nowadays, in addition to |
| 30 |
4.8.2. Limit Setuid and Setgid File and Directory Usage |
| 31 |
we've to also check for SECURITY_FILE_CAPABILITIES and `getcat`. |
| 32 |
|
| 33 |
5) In my experience, while |
| 34 |
4.8.5. Review File Integrity Regularly |
| 35 |
looks like good idea, it's nearly impossible to use in Gentoo because |
| 36 |
of daily updates which change a lot of system files, so it's too hard |
| 37 |
to review aide-like tool reports and quickly detect suspicious file |
| 38 |
changes. If anyone have a good recipe how to work around this I'll be |
| 39 |
glad to learn it. |
| 40 |
|
| 41 |
-- |
| 42 |
WBR, Alex. |
Archives