[scponly] Scponly 4.8 on Debian 4.0 64bit

[Valkuma]

Hmm ok,

first when i set debuglevel to 1 nothing is logged to /var/log/syslog

Then i found out that if you set debuglevel from 2 to 1 SFTP works great
I think that the SFTP Client or SFTP server closed the connection when
it get the debug log in stdout.


But why is nothing logged to syslog ??
RegardlessI think to recompile it.

thanks for help. Do you think about add full 64bit support from download
in 4.9 oder 4.8.1?

Am 17.03.2010 17:12, schrieb Kaleb Pederson:
> On Wed, Mar 17, 2010 at 9:04 AM, Valkuma <valkuma at googlemail.com> wrote:
>   
>> Hello, thanks for your answer.
>>
>> How  can i retrive debug info for sftp? The only output i get is dow
>> there in my first post.
>>     
> First, you need to set a flag in the 'debuglevel' file:
>
> echo "1" > $SCPONLY_INSTALL_PREFIX/etc/scponly/debuglevel
>
> Once that's set, you should get syslog output when you try to connect
> to the sftp server.  It will look something like the following:
>
> scponly[21249]: chrooted binary in place, will chroot()
> scponly[21249]: 3 arguments in total.
> scponly[21249]:   arg 0 is 'scponlyc'
> scponly[21249]:   arg 1 is '-c'
> scponly[21249]:   arg 2 is '/usr/lib64/misc/sftp-server'
> scponly[21249]: opened log at LOG_AUTHPRIV, opts 0x00000009
> scponly[21249]: determined USER is "kalebp" from environment
> scponly[21249]: retrieved home directory of "/home/scponly//pub" for
> user "scponly"
> scponly[21249]: Setting homedir to /pub
> scponly[21249]: chrooting to dir: "/home/scponly"
> scponly[21249]: chdiring to dir: "/pub"
> scponly[21249]: setting uid to 107
> scponly[21249]: winscp_compat mode, argc=3
> scponly[21249]: processing request: "/usr/lib64/misc/sftp-server"
> scponly[21249]: Using getopt processing for cmd /usr/lib/misc/sftp-server
> (username: kalebp(107), IP/port: 127.0.0.1 37088 22)
> scponly[21249]: running: /usr/lib/misc/sftp-server (username:
> kalebp(107), IP/port: 127.0.0.1 37088 22)
> scponly[21249]: about to exec "/usr/lib/misc/sftp-server" (username:
> kalebp(107), IP/port: 127.0.0.1 37088 22)
>
> If you get something similar to the above but see a "Connection
> closed" message on your terminal, than the sftp-server is being run
> correctly but is missing dependencies or something else that's causing
> it to run.  The FAQ page contains some details on how to hunt these
> down using strace.
>
> --
> Kaleb Pederson
>
> Blog - http://kalebpederson.com
> Twitter - http://twitter.com/kalebpederson
>