ssh working, but not sftp..

[J. Zyphichore]

i've been reading through alot of the ssh/sftp-subsystem posts
(especially those dealing w/ windows ssh.com clients and OpenSSH
servers) but i'm still encountering the following "classic?" problem:

i can ssh (from a windows ssh.com.3.1.0-235 to an OpenSSH.3.0.2p1-1
server), but whenever i try to open an sftp session using the latest
ssh.com client, it gives me the old "Connection Lost.." routine.
(Vandyke's SecureFX works though, too bad i can't buy enough licenses
for eveyone who needs to sftp to our server.. :/ )

these seemed to have fixed 99% "sftp connects" that other people have
had trouble w/, but not mine:

- Subsystem sftp /usr/libexec/openssh/sftp-server
- sftp-server's in the users path (server side)

any ideas? (i *know* i'm gonna feel silly when i find out it's
something obvious :)

--

i'm still wading thru the debug & trying to compare a few things but
just in case anyone else has this problem:

debug1: input_session_request
debug1: channel 1: new [server-session]
debug1: session_new: session 1
debug1: session_open: channel 1
debug1: session_open: session 1: link with channel 1
debug1: server_input_channel_open: confirm session
debug1: session_by_channel: session 1 channel 1
debug1: session_input_channel_req: session 1 channel 1 request
auth-agent-req reply 0
debug1: session_by_channel: session 1 channel 1
debug1: session_input_channel_req: session 1 channel 1 request
subsystem reply 1
subsystem request for sftp
debug1: subsystem: exec() /usr/libexec/openssh/sftp-server
debug1: PAM establishing creds # hmm.. 600 ok on
/etc/pam.d/sshd?
debug1: fd 10 setting O_NONBLOCK # maybe pam > 0.72-20.6.x req?
(rh 6.2)

# lost connection on client here, [hit ok] prompt

debug1: channel 1: rcvd eof
debug1: channel 1: output open -> drain
debug1: channel 1: obuf empty
debug1: channel 1: output drain -> closed
debug1: channel 1: close_write
debug1: Received SIGCHLD.
debug1: session_by_pid: pid 1236
debug1: session_exit_message: session 1 channel 1 pid 1236
debug1: session_exit_message: release channel 1
debug1: session_close: session 1 pid 1236
debug1: channel 1: read<=0 rfd 10 len 0
debug1: channel 1: read failed
debug1: channel 1: input open -> drain
debug1: channel 1: close_read
debug1: channel 1: ibuf empty
debug1: channel 1: input drain -> closed
debug1: channel 1: send eof
debug1: channel 1: send close

# closed client/sftp app here

debug1: channel 1: rcvd close
debug1: channel 1: is dead
debug1: channel 1: garbage collecting
debug1: channel_free: channel 1: server-session, nchannels 2

[Dan Oviatt]

I just recently had the same problem. It was the permissions on
sftp-server. One of the admins changed it to 550 and unless you were
the owner or in the right group you had no permission to execute it.
Change sftp-server to 555 or 755 and see if that helps.

zyphi...@excite.com (J. Zyphichore) wrote in message news:<175863b2.01121...@posting.google.com>...

[J. Zyphichore]

solved:

http://www.openssh.com/faq.html#2.9

tweaked etc/user login/cshrc scripts:

if( $?prompt == 0 ) exit <-- (a single echo before the interactive
shell check was the culprit. i know, i know).. i've been using these
base scripts for almost 10 yrs w/o any problems accross 5 different
platforms and i never even thought of this as a side effect.. or just
sloppy shell scripting that never got caught by anything.. until now
:/

blah..