You mean someone compromised the system, I don’t think so. I like paranoid setup and I’ve hardened the system.
I like paranoid setup and I’ve hardened the system.
And that is the problem…
Because someone has played???
Not someone, you…
Yeah, I tinker. VMplayer works though.
[quote="“chigurh,post:43,topic:135424”]
Yeah, I tinker. VMplayer works though.[/QUOTE]
With problem I mean the installing of Virtualbox, not you as problem…
So please excuse…
No worries.
Hmmm …
Whether or not a system running Virtual Machines needs to suffer a Paranoid setup and, be hardened, is a topic which needs some discussion.
IMHO, the VM implementers are usually not expecting a SELinux system – you’ll need to dig into the Oracle VirtualBox documentation for hints as to what is needed if the Linux system security has been tightened up …
Which begs the question, why?
- AFAICS, anything running in a VM can not, usually – there’s possibly a way but, – access the Linux Kernel running the VM – a VM implementation, AFAIK, doesn’t usually have any “Back Doors” or “holes” which allow the system being hosted in the VM to access the Kernel hosting the VM …
- And, access from the Linux Kernel to the system(s) being hosted by the VM(s) is also not, usually, possible.
- The only exception is, the shared directories where files can be shared between the system(s) in the VM(s) and the Linux system hosting the VM(s) …
- Plus any network connections …