> I can't think of anything more painful than trying to run zmodem through
> an already secure and reliable connection that can even do compression,
> no matter how many files you have to transfer or how many times you have
> to re-write similar scripts to do multi-file transfers.
>
> Of course without knowing what platform(s) you're using I can't say for
> sure why something like "scp * remote.host:" doesn't work for you, or
> how hard it might be to write a script to do multi-file transfers
Really simple reason, regardless of double-compression and whatever. Let's
say I have 5 files named file1-file5 on a remote system that I am currently
SSHed in to.
[ SSH Model ]
remote% ls
file1 file3 file5
file2 file4
remote% exit
logout
local% scp remote:file1 .
password: .....
local% scp remote:file2 .
password: .....
local% scp remote:file3 .
password: .....
local% scp remote:file4 .
password: .....
local% scp remote:file5 .
password: .....
[-- Don't forget that 'scp remote:file* .' doesn't work... --]
local% ssh remote
[ SZ Model ]
remote% sz file[1-5]
remote%
uh.. yeah. Easier. Silly, in a protocol kind of way, but easier. Also,
don't forget what how strong authentication can change the picture..
local% scp remote:file1 .
Cryptocard Challenge: 25401877
Response: ........
local% scp remote:file2 .
Cryptocard Challenge: 37564211
Response: ........
..or pity the SecurID users who must wait 60 seconds between each transfer.
--
Joe Rhett Systems Engineer
[EMAIL PROTECTED] ISite Services
PGP keys and contact information: http://www.noc.isite.net/Staff/
