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

[Mark Trolley]

I'm going backwards here. Now I can't even get those few lines of log
messages in auth.log that I showed you in my previous email, and I
can't find any other logs containing anything useful. I'm extremely
confused why it stopped altogether.

Do I need to change any other files? sshd_config? I added to
/etc/shells and that was it.

I've even tried using scponly instead of scponlyc and get exactly the
same thing:

Apr  7 08:47:47 hanzy sshd[2999]: debug1: subsystem: exec() /usr/lib/sftp-server
Apr  7 08:47:47 hanzy scponly[3000]: 3 arguments in total.
Apr  7 08:47:47 hanzy scponly[3000]: ^Iarg 0 is scponly
Apr  7 08:47:47 hanzy scponly[3000]: ^Iarg 1 is -c
Apr  7 08:47:47 hanzy scponly[3000]: ^Iarg 2 is /usr/lib/sftp-server
Apr  7 08:47:47 hanzy scponly[3000]: opened log at LOG_AUTHPRIV, opts 0x00000029
Apr  7 08:47:47 hanzy sshd[2999]: debug1: Received SIGCHLD.



On Mon, Apr 6, 2009 at 12:44 PM, Kaleb Pederson
<kaleb.pederson at gmail.com> wrote:
> On Mon, Apr 6, 2009 at 9:23 AM, Christopher Barry
> <christopher.barry at qlogic.com> wrote:
>> I've been working with logging myself a lot lately, and one thing on Debian/Ubuntu I found necessary was in the file /etc/default/syslogd add in:
>> SYSLOGD="-a /path/to/chroot/dev/log"
>>
>> This will auto-create a syslog socket for you so sftp-server can write to the log.
>
> Yes, this is important when you want the sftp-server to do the
> logging.  It is not important, however, for scponly to log  as scponly
> attaches to the logging service before it does the chroot.
>
> --Kaleb
>
> _______________________________________________
> scponly mailing list
> scponly at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/scponly
>