Nikos Mavroyanopoulos <[EMAIL PROTECTED]> writes:
> I've been trying to use the sftp program with lsh...
Interesting. I don't know at all how sftp works.
> Since it executes sftpserv on the remote side i've tried "lsh remove
> sftpserv", "lsh remote -E sftpserv", "lsh remote -S=/path/sftpserv"
> but none of them seem to work.
lsh remote sftpserv
lsh -E sftpserv remote
should do exactly the same thing. -S is quite different. If sftpserv
is not in your PATH, you may want to use an absolute filename.
> The server is an ssh v2.0.13 server and the client is lsh-0.9.9.
> I attach you the output of lsh --trace and -v:
>
> [...]
> Allocated local channel number 0
> Registering local channel 0.
> Taking channel 0 in use, (local 0).
> Entering lsh_start_session
> lsh: Requesting remote exec.
> Leaving lsh_start_session, value of type client_session.
> Leaving make_start_session, value of type client_session.
> Leaving make_lsh_connect, value of type client_session.
> Sending EOF on channel 0
> Receiving CLOSE on channel 0 (local 0)
This usually happens if the remote process dies early, for example if
exec() fails.
You may also want to try running sftp with the ssh2, connecting to
an lshd server. If you run lshd with the --debug flag, you get packet
dumps that may help figure out what sftp is doing. I was under the
impression that sftp doesn't use the "exec" request, but rather a
"subsystem" request. But I don't realy know.
/Niels
