Re: [Boa Constr] SSHExplorer

[Yuppie <sc...@we...>]

Hi Riaan!


Many thanks for your reply!

> Me! I use it to browse my SourceForge shell account and copy files
> to/from it. My one and only test case :)

Interested in some more test results? Today I took a closer look at SSH.

I tested on 3 accounts:
user@irixhost: irix, OpenSSH
user@linuxhost: linux, OpenSSH
user@windowshost: windows, OpenSSH/cygwin, boa

> >My experiments:
> >
> >- I managed to browse the remote filesystem
> >     o  using the absolute root path ("/home/user", not "~")
>
>
> I assume you mean you changed the property 'root' of the SSH
> connection.

Right.

> You *should* change this (as you did) to wherever you need.
> It's a property in the Inspector after all!
> ~ still sounds like a valid default that has a better chance
> of working that any other default value.

Yes and no.

The '~'-problem:
================
~ is expanded on the local machine. If home path is not the same on 
local and remote machine, SSHExplorer fails.

[user@irixhost]: echo $home
/home/u/user
[user@linuxhost]: echo $home
/home/user
[user@windowshost]: echo %home%
C:\myhome

[user@irixhost]: ssh -l <user> <linuxhost> ls -la ~
ls: /home/u/user: not found
[user@windowshost]: ssh -l <user> <linuxhost> ls -la ~
ls: /myhome: not found

[user@irixhost]: ssh -l <user> <linuxhost> ls -la \~
works
[user@windowshost]: ssh -l <user> <linuxhost> ls -la \~
ls: ~: not found

[user@irixhost]: ssh -l <user> <linuxhost> ls -la '~'
works
[user@windowshost]: ssh -l <user> <linuxhost> ls -la '~'
works
[user@windowshost]: ssh -l <user> <linuxhost> ls -la '~'/folder
works
[user@windowshost]: ssh -l <user> <linuxhost> 'ls -la ~/folder'
works

Quoting seems to be the solution, at least on cygwin and unix. Changed 
the property 'root' from "~" to "'~'" and browsing works fine for me.

> >- I tried to open files from remote filesystem
> >     o  copyToFS and copyFromFS seem to use pscp, not my scp
> >
> >My questions:
> >
> >- Is pscp PuTTY-scp? Does SSHExplorer work if I install this?
>
>
> Yes, it's putty scp. The only scp I could get to work (see below).

Did not install this so far.

> After testing scp again it seems to be working now!
> Granted I'm not on the same machine I was when I wrote SSHExplorer,
> but I have no idea what has changed in the meanwhile.
>
> The new problem I now have is that scp does not accept windows
> paths. (Seems to be a quick and dirty port)
>
> e.g.
> scp  text.txt
>
> copies fine, but
>
> scp  c:\text.txt
>
> gives an error :/
>
> One way to work around this would be to change the current directory
> to the localpath directory before running the command.

Same Problem with OpenSSH.

> I'll implement the current directory hack, that should work for both
> of us and also on Linux.

+1

> For you this change should be sufficient:
>
>     def buildSCPStrs(self, source, dest):
>         return 'scp %s %s'%(source, dest), 'scp %s %s'%(source, dest)

Well. Actually that's the last thing I tried before writing to the 
mailinglist.

The ':'-problem:
================
scp syntax uses ':' to seperate <host> from <file>. c:\filename is 
interpreted as host = "c" and file = "\filename".

[user@windowshost]: scp <user>@<linuxhost>:file c:\folder
ssh: c: no address associated with hostname.
[user@windowshost]: scp <user>@<linuxhost>:file /folder
works
[user@windowshost]: scp <user>@<linuxhost>:file /cygdrive/c/folder
works

Any hints where to change the local path?


TIA,

Yuppie