Carlos Carvalho wrote:
> Greg A. Woods ([EMAIL PROTECTED]) wrote on 17 January 1999 01:04:
> >I suspect that your real complaint is that your current configuration
> >requires you to type your password for every file to be copied or some
> >such. You should be able to avoid that with the "scp * remote:" style
> >of command-line, but you should also be able to set up your
> >authentication such that you don't ever have to enter a password.
>
> How??? I'm facing this exact same problem now. I'm considering
> blocking telnet so that people from home are obliged to use ssh and
> stop sending passwords in the clear (we've had two invasions already
> from someone who knew the password). The problem is that I'll allow
> only RSA authentication, and the user therefore WILL HAVE to enter the
> password for each scp connection they make...
>
> The only work-around I know for this is to use ssh-agent, but from
> home people will only be using rwin-dows, and it doesn't exit in the
> teraterm implementation of rwin-dows :-(
I use sz/rz from Teraterm/TTSSH quite often. It's fine as long as you don't
have to transfer a lot of files. (If lots of related files are involved I
sometimes just transfer a ZIP file.)
I don't know of any ssh-agent implementations for Windows. I don't even
know what interface TTSSH would use to communicate with a Windows
ssh-agent.
Workarounds: using SSH to tunnel FTP connections, or better yet, using SSH
to tunnel SMB file sharing connections to a machine running Samba (or NT,
if you're stuck with that).
Rob
--
[Robert O'Callahan, http://www.cs.cmu.edu/~roc, 5th year CMU CS PhD student
Upgrade your export version Communicator 4.5 to full-strength crypto:]
#!/usr/bin/perl5 -0777pi # Run on your "netscape" binary
s/KEY-BITS:.*?\0/$_=$&;y,a-z, ,;s, 512,2048,;s, {4}$,true,gm;$_/es;
s!\*:Q\xbf/q.{46}(.).{33}!substr($t=$&,54,ord$1)=~y,,\1,c;$t!egs
