[scponly] scponly working intermittently

[Kaleb Pederson]

On Tue, Nov 4, 2008 at 9:59 AM, Addison Laurent <alaurent at westga.edu> wrote:
> scp fails consistently, sftp works sometimes.
> No obvious errors are being logged.
...
> Gentoo Linux, Kernel 2.6.19 x86_64 AMD Opteron (Sun v40z server).
> OpenSSH 5.1_p1-r1
> PAM  1.0.1

Gentoo doesn't currently enable scp support.  I'm not sure if they
ever have or if that behavior has changed, but right now the
configuration step looks like the following:

src_compile() {
    econf \
        --disable-wildcards \
        --enable-chrooted-binary \
        --disable-gftp-compat \
        --with-sftp-server="/usr/$(get_libdir)/misc/sftp-server" \
        $(use_enable rsync rsync-compat) \
        $(use_enable subversion svn-compat) \
        $(use_enable subversion svnserv-compat) \
        || die "./configure failed"
    emake || die
}

[...snip...]
> Nov  4 12:49:01 stuweb scponly[8784]: Using getopt processing for cmd
> /usr/lib64/misc/sftp-server  (username: alaurent(44796), IP/port: [ip]
> 62487 22)
> Nov  4 12:49:01 stuweb scponly[8784]: running:
> /usr/lib64/misc/sftp-server (username: alaurent(44796), IP/port: [ip]
> 62487 22)
> Nov  4 12:49:01 stuweb sshd[8777]: pam_unix(sshd:session): session
> closed for user alaurent

Comparing the source log to the failure log doesn't really help.
Unless configured with support for winscp compatibility, there is
literally not a single line of code between the "running: %s (%s)"
line and the "about to exec \"%s\" (%s)" line.

I do, however, remember getting a possibly-related bug report from
someone running on a non-Linux system that I have patched in CVS.  I'd
recommend that you try it and let me know if it helps.

Good luck.

--Kaleb