[scponly] scponlyc broken after upgrade to Debian 5

[Kaleb Pederson]

On Tuesday 10 March 2009 12:58:10 pm Chris Wood wrote:
> > Those don't make sense unless the WinSCP compatibility mode detection was quite broken or your sftp client is doing something > quite strange.  The test for WinSCP compatibility mode shouldn't be something that's not likely to happen accidently, as the >program requested by the connecting client would have to match:
> 
> Actually, what you quote above is the output on my putty screen when I
> was testing it via putty.  That is a separate test from the other log
> files I included in my email which are of my sftp attempt from a linux
> box.  Sorry I didn't explain that very well.

No problem.  What does the scponly log output look like when you're connecting using Linux? I'm looking for output similar to the putty output, indicating what was executed on the server running scponly and what decisions scponly made based on its input.

> >
> > If the above doesn't help, I'd follow the instructions on the FAQ to generate a full set of strace files:
> 
> 
> I have followed this FAQ and the strace is included in my original
> post which is a strace of my sftp attempt from one linux client to the
> server.

On a Linux box, you should have had more than one strace file, I'm interested in seeing all of them.

But, like I said, please try the latest version of scponly first. scponly-4.6 was released over three years ago.  Scponly 4.8, the latest stable release, was released over a year ago.  I'd like to make another release soon, but I haven't had time to track down some autoconf stuff that needs to be changed (for a few edge cases).

Thanks.

--Kaleb