On Wed, Mar 22, 2006 at 09:49:34AM +0000, Daniel Carrera wrote: > 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.
--yes David _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
