Difference between revisions of "Talk:Secure chroot Barrier"

From Linux-VServer

Jump to: navigation, search
(billige nike sko,nike shox sko tilbud: new section)
m (Reverted edits by FaltWasttep (talk) to last revision by Powerfox)
(6 intermediate revisions by 4 users not shown)
Line 17: Line 17:
  
 
# Accoring to http://oldwiki.linux-vserver.org/Step-by-Step+Guide+2.6: "On Linux 2.6 this isn't really necessary, since another mechanism is used to lock in the guests anyway" - maybe someone could elaborate on this and put it in the article, please
 
# Accoring to http://oldwiki.linux-vserver.org/Step-by-Step+Guide+2.6: "On Linux 2.6 this isn't really necessary, since another mechanism is used to lock in the guests anyway" - maybe someone could elaborate on this and put it in the article, please
 
== billige nike sko,nike shox sko tilbud ==
 
 
http://nikeskoene.com/ Nike Shox Sko Tilbud,Sko Nike Shox,Nike Shox NZ Sko,Shox Nz Sko,Shox R4 Sko,Nike Shox NZ,Nike Shox R4 Sko
 
http://nikeskoene.com/ Billige Air Max Sko,Billige Shox Sko,Billige Nike Sko,Air Max Sko Nike
 

Revision as of 04:33, 10 April 2013

  1. setattr --barrier /vservers
  2. showattr /vservers
  • NOTE: when setting xattrs on reiserfs, please not that the filesystem has to be mounted explicitly with 'attrs' option, i.e.: mount /dev/reiserfsdev /vservers -oattrs to get the barrier survive after umount/reboot.

Seems insufficient. You need to set --barrier for every existing and NEW directory except those below /vservers/. as the suggested command protects only against chdir ..

Why? The fchdir.

Am I right?

once you gain root inside the scure chroot:

may you gain access to the device node?

i/o ports not restricted?


  1. Accoring to http://oldwiki.linux-vserver.org/Step-by-Step+Guide+2.6: "On Linux 2.6 this isn't really necessary, since another mechanism is used to lock in the guests anyway" - maybe someone could elaborate on this and put it in the article, please
Personal tools