On 3/16/07, Daniel Hokka Zakrisson <daniel@hozac.com> wrote:
> Daniel W. Crompton wrote:
>> After reading Jean-Marc's answer I thought it could also be the fact
>> that you might just need to create /dev/mem.
>
> You absolutely never ever want to do that, if you care the least about the
> guest being secure... /dev/mem would give it complete access to the
> contents of your RAM.
Seriously if you care about your guest being secure you make sure that
the host doesn't have physical network access. If you want to be able
to run certain programs in a guest you sometimes need rights which are
available to only the host. That's the whole point of caps.
I want to make it clear that I have no idea what the OCS program does,
but if you want to run it in a guest then you need to be able to
access /dev/mem. Making the guest insecure is the price you have to
pay. Having network access for a machine means risking remote attacks
it's the price you pay.
I hardly run anything on my host systems besides syslog and sshd,
practically everything runs in a guest. Some guests have caps that
give it almost full access to the host system on other guests you
don't even have write access to the disk or a compiler. (It logs to
the host's syslog anyway.) The level of access you need in a guest
determines who access is given to, not whether you do something or
not.
The only thing you "absolutely never ever" want to do is give somebody
you don't trust physical access to the host, anything else is a
question of need.
D.
blaze your trail
-- redhat _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Sat Mar 17 12:27:45 2007