1 |
Hans-Thomas Mueller napisa³(a): |
2 |
> Another option instead of Xen or SELinux is to set up vservers_, with |
3 |
> Grsec+Pax. The performance impact is minimal but you still get clean |
4 |
> and isolated environments for your services. |
5 |
> |
6 |
> SELinux gives some additional security indeed but is quite expensive to |
7 |
> administer -- unless you run only pre-configured packages on your |
8 |
> server. Once you start running your own software you spend much time |
9 |
> writing policies. I have run some SELinux servers a while ago and I |
10 |
> won't do it again unless absolutely necessary. I see the use of SELinux |
11 |
> mainly in fine-grained control of interactions of human users with shell |
12 |
> accounts in a high security environment. Servers should be as simple as |
13 |
> possible, I think. |
14 |
> |
15 |
> Regards, |
16 |
> Hans-Thomas |
17 |
|
18 |
I have my server for about a year and I didn't have serious problems, |
19 |
but it has only few services running: firewall, web cache, dhcp, ntp, |
20 |
nfs, dns. |
21 |
|
22 |
There is also so called "targeted policy". It protects daemons, but runs |
23 |
other processes in a role that has access to everything. |
24 |
|
25 |
Thus, when you want to run only commonly used daemons (that have |
26 |
policies), or when you choose targeted policy, SELinux isn't very hard |
27 |
to use. |
28 |
|
29 |
Regards, |
30 |
Marek Wróbel |
31 |
-- |
32 |
gentoo-hardened@g.o mailing list |