SSH-1.99-OpenSSH_3.1p1
Anyone know if there's a simple answer as to why I cannot connect?
Thanks.
-Ken
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending subsystem: sftp
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.2 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
Connection closed
sftp and/or scp may fail at connection time if you have shell
initialization (.profile, .bashrc, .cshrc, etc) which produces output
for non-interactive sessions. This output confuses the sftp/scp
client. You can verify if your shell is doing this by executing:
ssh yourhost /usr/bin/true
If the above command produces any output, then you need to modify your
shell initialization.
I tried that and got:
jailshell: /usr/bin/true: No such file or directory
I forgot about that. To the hosting company's credit, they gave me a
shell, though no one else gets one. I wonder if there's a simple way
around this. Anyone?
Thanks.
-Ken
Woops. Sorry for all the replies to myself, but if I try:
sh unix.vi /bin/true
I get no output at all, which I take as a good thing. But I still
cannot sftp there.
Thanks for any info.
-Ken
>I get no output at all, which I take as a good thing. But I still
>cannot sftp there.
I can't see a lot of point in sftp. Does scp work on your stuff ?
--
Elvis Notargiacomo http://www.sendacow.org.uk/homepage.html
> >I get no output at all, which I take as a good thing. But I still
> >cannot sftp there.
> I can't see a lot of point in sftp. Does scp work on your stuff ?
I haven't tried it. I like to have my ftp shell to be able then to
look at files remotely and locally and such.
-Ken