[scponly] FreeBSD 6.2 with chroot "Connection Closed"

Gregory L. Magnusson glm at cyborgspiders.com
Fri Dec 15 13:38:09 EST 2006


Make sure this line is uncommented
Subsystem sftp /usr/lib/openssh/sftp-server

Have you added your scponly user to the /etc/ssh/sshd_config file?
AllowUsers Anish christine Sputnik etc

-------------------------------------
After updating my FreeBSD install to 6.2-RC1 I can't seem to created new
scponly chrooted environments correctly. When I connect and enter the
password I just get a "Connection Closed" message. The existing scponly
chroots are fine, so it seems to be a problem with some of the update
FreeBSD files from 6.1 to 6.2. The problem only occurs in a chroot, if I
don't use a chroot it works fine.

>From my auth.log: Dec 15 02:35:35 hosting sshd[28827]: Accepted
keyboard-interactive/pam for myuser from 24.210.75.119 port 61528 ssh2
Dec 15 02:35:36 hosting sshd[28830]: subsystem request for sftp Dec 15
07:35:36 hosting scponly[28831]: changing initial directory to incoming
Dec 15 07:35:36 hosting scponly[28831]: running:
/usr/libexec/sftp-server (username: myuser (1014), IP/port:
24.210.75.119 61528 22) I've tried to enable sftp logging and even
applied the patch linked to yesterday, but when I add the -f AUTH -l
DEBUG to the sftp-server line the auth.log only shows: Dec 15 02:35:35
hosting sshd[28827]: Accepted keyboard-interactive/pam for myuser from
24.210.75.119 port 61528 ssh2 Dec 15 02:35:36 hosting sshd[28830]:
subsystem request for sftp Dec 15 07:35:36 hosting scponly[28831]:
changing initial directory to incoming So it doesn't seem to be even
calling sftp-server. This doesn't seem to be an scponly problem, but how
do I get sftp debug output enabled so that I can see what is wrong with
my setup? OpenSSH_4.5p1 scponly-4.6 Thanks,
-- Anish Mistry



More information about the scponly mailing list