Secure chroot Barrier - Revision history

Glenn: spelling

2011-10-21T19:00:11Z

spelling

2011-10-21T18:53:16Z

+cat

2009-09-16T01:29:47Z

Undo revision 3900 by 193.231.72.8 (Talk)

2009-09-15T11:26:08Z

‎Breakout Methods

2008-08-01T16:19:03Z

changing filesystem <-> mountpoint in my understanding

2008-02-28T20:12:59Z

‎Solution: Secure Barrier

2007-10-03T14:23:46Z

‎Solution: Secure Barrier

2007-09-04T13:27:55Z

‎Solution: Secure Barrier

2007-07-18T21:33:37Z

‎Solution: Secure Barrier

2007-02-24T18:55:04Z

remove superfluous {

← Older revision		Revision as of 19:00, 21 October 2011
Line 330:		Line 330:
	''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''		''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''

−	[[Category:~~Documentaion~~]]	+	[[Category:Documentation]]

← Older revision		Revision as of 18:53, 21 October 2011
Line 329:		Line 329:

	''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''		''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''
		+
		+	[[Category:Documentaion]]

@@ Line 319: / Line 319: @@
 </pre>
-If you keep all the guests in one filesystem, setting the barrier on /vservers is enough, otherwise it should be repeated for each mount point.
+If you keep all the guests in one mountpoint, setting the barrier on /vservers is enough, otherwise it should be repeated for each mount point.
 If you want to be safe you may choose to just set the barrier for each individual guest, for example:

@@ Line 319: / Line 319: @@
 </pre>
-''(note: strictly speaking this is incorrect, instead one wants to do <tt>setattr --barrier /path/to/guest/..</tt> for all guests, which can be quite different from the above, even for guests in /vservers *Bertl*)''
+If you keep all the guests in one filesystem, setting the barrier on /vservers is enough, otherwise it should be repeated for each mount point.
-'' Please note that the ".." at the end of the /path/to/guest/.. has to be present''
+If you want to be safe you may choose to just set the barrier for each individual guest, for example:
 ''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''

← Older revision		Revision as of 14:23, 3 October 2007
Line 320:		Line 320:

	''(note: strictly speaking this is incorrect, instead one wants to do <tt>setattr --barrier /path/to/guest/..</tt> for all guests, which can be quite different from the above, even for guests in /vservers Bertl)''		''(note: strictly speaking this is incorrect, instead one wants to do <tt>setattr --barrier /path/to/guest/..</tt> for all guests, which can be quite different from the above, even for guests in /vservers Bertl)''
		+
		+	'' Please note that the ".." at the end of the /path/to/guest/.. has to be present''

	''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''		''(note: <tt>---Bui-</tt> barrier set, <tt>---bui-</tt> barrier available and not set)''

@@ Line 315: / Line 315: @@
 # setattr --barrier /vservers
 # showattr /vservers
 </pre>
 ''(note: strictly speaking this is incorrect, instead one wants to do <tt>setattr --barrier /path/to/guest/..</tt> for all guests, which can be quite different from the above, even for guests in /vservers *Bertl*)''

← Older revision		Revision as of 21:33, 18 July 2007
Line 316:		Line 316:
	# showattr /vservers		# showattr /vservers
	</pre>		</pre>
		+
		+	''(note: strictly speaking this is incorrect, instead one wants to do <tt>setattr --barrier /path/to/guest/..</tt> for all guests, which can be quite different from the above, even for guests in /vservers Bertl)''

@@ Line 57: / Line 57: @@
+	}
-	if (chroot(".") != 0) {
+	if (chroot(".") != 0)
 		die("chroot(.)");