"Neal H. Walfield" <[EMAIL PROTECTED]> writes: > Breaking out of a chroot on the Hurd is trivial: just use a passive > translator. A passive translator will inherit the namespace of the > file system which started it, not the process which set it. Thus, a > chroot'ed user need only run: > > settrans -c root /hurd/firmlink / > > Neighbor Hurds won't suffer from this problem. > > I don't have any ideas offhand of how this could be fixed.
It's easier than that; you can just directly ask the proc server for the global system root. The Hurd doesn't have Unixy chroots by design, but you can make a subhurd which you can't break out of. That's the correct way to solve the problems that Unix solves with chroot. Thomas _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
