Set up RSA/DSA public key authentication and no password will be needed. Then
run scp unencrypted to send the previously encrypted data.
I believe the public key authentication encrypts a challange with the private
key which is verified by the server decrypting with the public key found in
authorized_hosts* or in the file pointed to in the authorization file (depending
on whether DSA or RSA is used and whether the server is running OpenSSH or
SSH.com. Thus, the only thing that would be seen on the wire is the encrypted
challange.
--Dave
>Date: Sat, 20 Jan 2001 21:11:33 -0500 (EST)
>X-Authentication-Warning: cfa0.harvard.edu: peprbv set sender to
[EMAIL PROTECTED] using -f
>From: Bob Babcock <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: scp performance.
>
>> > You might get the best results by pre-encrypting your files and then using
>> > normal FTP to transmit them.
>>
>> Yep, that's plan b.
>
>But that would leave your logon information unsecured which might be worse
>than not protecting the data. Can scp/sftp be told to only encrypt the logon
>information, not the data?
--
David Knight French
Black Mountain Computer Consulting
Voice: (858)279-4862
Email: [EMAIL PROTECTED]
