On 08/10/02 16:23 +0100, Trevor Cushen wrote: <snip> > I want to go SSH and have the encryption but the work involved is hard > to justify to the customer (because the work is their side, as in > rewrite the scripts). The argument that Ettercap claims to break SSH > must also be throw into the mix here too. > I could use stunnel if I just wanted encryption???? You could, but that probably would be more work. <snip> > client will not be prompted for a password. In that case accountability > is at the machine level. If I am wrong please inform me gently as I This is correct. Machine and user level. So there really will be no major change in the scripts, except for the first time key exchange. Once the keys are set up properly, you can just ssh user@remotehost or scp user@remote:/path/to/file /path/to/local or the other way round. There should be no major script change, except s/rsh/ssh/g
Devdas Bhagat
