Difference between revisions of "Talk:Secure chroot Barrier"

From Linux-VServer

Jump to: navigation, search
(I like it - replica rolex: new section)
m (Reverted edits by PeftSoate (talk) to last revision by Powerfox)
 
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
 
== I like it - replica rolex ==
 
 
http://www.4shared.com/office/Vyqcuq2o/rolex_sea_dweller_replica.html
 
http://www.divshare.com/download/24180036-346
 
http://en.calameo.com/read/00248389233c3cef73745
 
http://depositfiles.com/files/hset3pq9e
 
http://www.authorstream.com/Presentation/barrybhall648-1839710-replica-rolex-cellini/
 

Latest revision as of 06:02, 5 June 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