Editing
Paper
(section)
From Linix VServer
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Linux-VServer Security == Now that we know what the Linux-VServer framework provides and how some features work, let's have a word on security, because you should not rely on the framework to be secure per definition. Instead, you should exactly know what you are doing. === Secure Capabilities === Currently the following Linux Capabilities are considered secure for VPS use. If others are added, it will probably open some security hole. * CAP_CHOWN * CAP_DAC_OVERRIDE * CAP_DAC_READ_SEARCH * CAP_FOWNER * CAP_FSETID * CAP_KILL * CAP_SETGID * CAP_SETUID * CAP_NET_BIND_SERVICE * CAP_SYS_CHROOT * CAP_SYS_PTRACE * CAP_SYS_BOOT * CAP_SYS_TTY_CONFIG * CAP_LEASE CAP_NET_RAW for example is not considered secure although it is often used to allow the broken ping command to work, although there are better alternatives like the userspace ping command poink[U7] or the VXC_RAW_ICMP Context Capability. === The Chroot Barrier === Ensuring that the Barrier flag is set on the parent directory of each VPS is vital if you do not want VPS root to escape from the confinement and walk your Host's root filesystem. === Secure Device Nodes === The /dev directory of a VPS should not contain more than the following devices and the one directory for the unix pts tree. * c 1 7 full * c 1 3 null * c 5 2 ptmx * c 1 8 random * c 5 0 tty * c 1 9 urandom * c 1 5 zero * d pts Of course other device nodes like console, mem and kmem, even block and character devices can be added, but some expertise is required in order to ensure no security holes are opened. === Secure Proc-FS Entries === There has been no detailed evaluation of secure and unsecure entries in the proc filesystem, but there have been some incidents where unprotected (not protected via Linux Capabilities) writable proc entries caused mayhem. For example, /proc/sysrq-trigger is something which should not be accessible inside a VPS without a very good reason.
Summary:
Please note that all contributions to Linix VServer may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Linix VServer:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
About
Overview
Paper
News
Developers
Donations
Search
Getting Started
Downloads
FAQs
Documentation
Support
Participate
How to participate
Report a Bug
Communicate
Teams/Projects
Hall of Fame
Resources
Archives
Recent Wiki Changes
Pastebin
Related Projects
VServer Hosting
Happy VServer Users
Tools
What links here
Related changes
Special pages
Page information