Barry Margolin wrote:
> He wants to save the encrypted version in a local file

Correct.

> so that he can then copy it multiple times without having to
> re-encrypt it each time.

That was speculation by another poster.

> Question for the OP: when you try to decrypt it at each destination,
> how do you expect that to work? When SSH is encrypting traffic
> between two hosts, it makes use of a public-key encryption algorithm
> to exchange the encryption key. But if you use SSH locally, and then
> transfer the file using a non-crypto protocol, how is the remote
> system going to find out what key to use to decrypt it?

I was expecting that the key used would have to reside on the
destination (sort of like how key based authentication works now with
authorized_keys2) and would need to be specified in the command line.

However it was shear conjecture, and as I expected SSH can't do this,
from all appearances. I do think I'm going to pose the question to the
OpenSSH guys though, as this is a potentially nice feature, even if it
is somewhat duplicating PGP/GPG functionality.

--
================================================== ==========