[scponly] SIGPIPE when trying to connect to chrooted scponly host

[Kaleb Pederson]

Mark,

On Sunday 05 April 2009 03:29:23 pm Mark Trolley wrote:
>Sorry, didn't realize my reply went straight to you.

It's alright, that happens.

>I don't know why it wasn't working but when I tried testing by
>connecting locally (# sftp user at localhost) I got that in my log.
>
>Here's what I get when I try from Filezilla from a remote host:
...

> Apr  5 18:27:38 hanzy sshd[13628]: subsystem request for sftp
> Apr  5 18:27:38 hanzy sshd[13628]: debug1: subsystem: exec()
> /usr/lib/sftp-server
> Apr  5 18:27:38 hanzy scponly[13629]: chrooted binary in place, will chroot()
> Apr  5 18:27:38 hanzy scponly[13629]: 3 arguments in total.
> Apr  5 18:27:38 hanzy scponly[13629]: ^Iarg 0 is scponlyc
> Apr  5 18:27:38 hanzy scponly[13629]: ^Iarg 1 is -c
> Apr  5 18:27:38 hanzy scponly[13629]: ^Iarg 2 is /usr/lib/sftp-server
> Apr  5 18:27:38 hanzy scponly[13629]: opened log at LOG_AUTHPRIV, opts
> 0x00000029

Are you sure that's the only output being generated by scponly?  You might check a couple of the other log files as we should see something indicating that scponly chrooted to the correct directory, changed directory, etc., but none of those is present in the above.

Thanks.

--Kaleb