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

[Mark Trolley]

I'll give that a try and post the results.

On Tue, Apr 7, 2009 at 10:56 AM, Kaleb Pederson
<kaleb.pederson at gmail.com> wrote:
> On Tuesday 07 April 2009 05:55:56 am Mark Trolley wrote:
>> If I run scponly or scponlyc manually it works:
>>
>> # sudo scpuser /usr/local/bin/scponly -c /usr/lib/sftp-server
>> scponly[3061]: 3 arguments in total.
>> scponly[3061]:  arg 0 is /usr/local/bin/scponly
>> scponly[3061]:  arg 1 is -c
>> scponly[3061]:  arg 2 is /usr/lib/sftp-server
>> scponly[3061]: opened log at LOG_AUTHPRIV, opts 0x00000029
>> scponly[3061]: determined USER is "scpuser" from environment
>> scponly[3061]: retrieved home directory of "/media/media/ftp" for user "scpuser"
>> scponly[3061]: setting uid to 1014
>> scponly[3061]: processing request: "/usr/lib/sftp-server"
>> scponly[3061]: Using getopt processing for cmd /usr/lib/sftp-server
>>  (username: scpuser(1014), IP/port: no ip?!)
>> scponly[3061]: running: /usr/lib/sftp-server (username: scpuser(1014),
>> IP/port: no ip?!)
>> scponly[3061]: about to exec "/usr/lib/sftp-server" (username:
>> scpuser(1014), IP/port: no ip?!)
>
>
> Hmm... that's the correct output.  Maybe scponly really is aborting before it gets a chance to chroot.  Do you have SELinux enabled?
>
> Nothing else comes to my mind.  You could try the CVS version of scponly, but I can't think of any changes that would help this.
>
> If you're comfortable editing code, you could add some lines like the following throughout the code:
>
> debug(LOG_DEBUG, "I made it to point A in the code");
>
> HTH,
>
> --Kaleb
>
> _______________________________________________
> scponly mailing list
> scponly at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/scponly
>