[scponly] segfault when trying to connect

[Tim Donnelly]

Kaleb,

I installed the snapshot version from your post to the list dated Jul 18 and
got the same results.  Below I have pasted the /var/log/messages output and
the trace output is available at the same location
(www.coalliance.org/public).

Jul 23 15:23:36 tester sshd[18661]: Accepted keyboard-interactive/pam for
scponly from 208.178.237.110 port 38253 ssh2
Jul 23 15:23:36 tester sshd[18664]: subsystem request for sftp
Jul 23 15:23:36 tester scponly[18665]: chrooted binary in place, will
chroot()
Jul 23 15:23:36 tester scponly[18665]: 3 arguments in total.
Jul 23 15:23:36 tester scponly[18665]:  arg 0 is scponlyc
Jul 23 15:23:36 tester scponly[18665]:  arg 1 is -c
Jul 23 15:23:36 tester scponly[18665]:  arg 2 is /usr/lib64/ssh/sftp-server
Jul 23 15:23:36 tester scponly[18665]: opened log at LOG_AUTHPRIV, opts
0x00000029
Jul 23 15:23:36 tester scponly[18665]: determined USER is "scponly" from
environment
Jul 23 15:23:36 tester scponly[18665]: retrieved home directory of
"/home/scponly" for user "scponly"
Jul 23 15:23:36 tester scponly[18665]: Looking at root_dir: /home/scponly
Jul 23 15:23:36 tester scponly[18665]: Looking at root_dir: /scponly
Jul 23 15:23:36 tester scponly[18665]: chrooting to dir: "/home/scponly"
Jul 23 15:23:36 tester scponly[18665]: chdiring to dir: "/"
Jul 23 21:23:36 tester scponly[18665]: setting uid to 1007
Jul 23 21:23:36 tester scponly[18665]: processing request:
"/usr/lib64/ssh/sftp-server"
Jul 23 15:23:36 tester kernel: scponlyc[18665]: segfault at 0000000000402c89
rip 00002b8aa095d972 rsp 00007fff0a2a1df0 e
rror 7

Any ideas?

-----Original Message-----
From: Kaleb Pederson [mailto:kibab at icehouse.net] 
Sent: Friday, July 20, 2007 4:58 PM
To: scponly at lists.ccs.neu.edu
Cc: Tim Donnelly
Subject: Re: [scponly] segfault when trying to connect

Thanks for the details Tim.

Can you try the latest CVS or the version I linked to a couple of days ago?

I'm not aware of any prcoblems in that area, but I would like to know that
this is fixed or fix the problem before our next release.

Thanks.

--Kaleb