ssh into chroot

I'm using schroot to run a sid chroot inside of etch, and have run into
a problem. I googled around, and found the following:

1. use bind to mount /proc inside the chroot
2. run sshd inside the chroot
3. connect

Only when I do these things, ssh seems to hang during the login process:

debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8

Obviously, it doesn't like the chroot somehow. What am I missing?

--
"Oh, look: rocks!"
-- Doctor Who, "Destiny of the Daleks"


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • sftp and chroot
    ... But, with sftp, i have a error message after entering password. ... debug1: fd 4 setting O_NONBLOCK ... debug2: fd 5 is O_NONBLOCK ... I have try sftp without chroot and it works fine. ...
    (comp.security.ssh)
  • Re: Ronning named in chroot env
    ... You can keep the number of libs that you need to put in the chroot down by ... If you are using the ports collection to build bind, ... > In case someone is interested in running named in chrooted environment on ... > FreeBSD, below is my experience how this can be done. ...
    (FreeBSD-Security)
  • Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind
    ... >:as user flags it would be trivial to have it the defaultt. ... > not be able to rebind its sockets), you can only restart it, and ... I'm not sure how bind handles restarts, but even if it execs over ... A shell script could copy the required shared libs into the chroot ...
    (FreeBSD-Security)
  • Re: Proper way to run bind9
    ... run if there is no chroot. ... I'll commit a fix for this in a second. ... >> file to run the system's version of bind, ...
    (freebsd-current)
  • Re: bind update keeps messing up write-rights
    ... Whenever I update bind it messes up/resets access rights on my ... You must have bind configured to run in chroot. ... Move your updateable zone files there and update the referenced paths in named.conf accordingly. ...
    (Fedora)