New encrypt-files option - CVS code
r.so at bigfoot.com
Tue Jan 8 20:22:01 CET 2002
since the addition of the "encrypt-files" option (or maybe earlier),
"default-recipient-self" is ignored together with the "encrypt"
option. I've always used "gpg -e file" to encrypt a file just for me
(I have default-recipient-self and default-key set in my options
file), but now GPG asks me for a recipient. "gpg --encrypt-files file"
does the job. Is this a bug or do I have to change all bash-scripts
from "--encrypt" to "--encrypt-files"?
And what is the real difference between "--encrypt" and
"--encrypt-files". I can read that "--encrypt" is for data now and
"--encrypt-files" for files, but what is the definition of data here.
Is it not recommended to use "--encrypt" for files from now on and if
yes, would this not result in a lot of broken scripts?
More information about the Gnupg-devel