Hi all,
Last question :)
By default, gpg will refuse to write to a file (myfile.gpg) that already
exists. Is there a way to change this behaviour?
I am running gpg on batch mode on a server to encrypt a database before
downloading. So I need to temporarily store the encrypted file on the
server. There are two ways to accomplish this:
1) Give Apache write permission to an entire directory, so it can add
and delete files in that directory.
2) Give Apache write permission to just one file (myfile.gpg) and keep
overwriting every time I download a new encrypted backup.
Right now I'm doing (1) but I guess that (2) would be better. But I can
only do (2) if I can confince gpg to overwrite an existing file.
I looked at the man page and FAQs and I couldn't find this information.
Thank you for your help.
Cheers,
Daniel.
--
/\/`) http://opendocumentfellowship.org
/\/_/
/\/_/ A life? Sounds great!
\/_/ Do you know where I could download one?
/
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
