Re: Chrooting OpensshFrom: Bennett Todd (firstname.lastname@example.org)
- Previous message: Charles Clancy: "Re: Chrooting Openssh"
- In reply to: Postmaster: "Chrooting Openssh"
- Next in thread: Jose Nazario: "Re: Chrooting Openssh"
- Reply: Jose Nazario: "Re: Chrooting Openssh"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 22 Oct 2001 09:41:34 -0400 From: Bennett Todd <email@example.com> To: Postmaster <firstname.lastname@example.org> Subject: Re: Chrooting Openssh Message-ID: <20011022094134.A17572@rahul.net>
> Does any body know to chroot openssh service?
Once upon a time, it was easy to set up chroot; just include copies
of all the programs you wanted to run in the chroot jail. Maybe one
or two would want a data file, you'd need to copy them in too, and
they'd give nice clear error messages telling you what you needed to
These days, though, chrooting has gotten hard. To chroot openssh you
need to chroot the ability to fire up a login shell, which means the
whole PAM machinery, as well as enough of /dev for both the
networking and the pty support. You'll probably need enough of /etc
for the name service switcher, and cthulhu only knows what else.
Likely most of the shared libraries on the system, dozens or
hundreds of them.
I suspect the easiest way to chase this will be to find a project
somewhere that's packaging tools for doing vhosting by chrooting.
I'm afraid I don't have a link for you, but hopefully "virtual host"
and "chroot" as keywords into search engines will turn up something.
I tried to set up chrooted openssh recently, after a long fight I
eventually gave up. Linux has turned really nasty that way,
everything depends on a zillion other subsystems.
- application/pgp-signature attachment: stored