On Mon, 8 Mar 2010 13:22, power...@powerman.name said:
I don't think so. Every project encrypt it backups with different
passwords (needed for security), and right now I can keep just several
dozens of passwords, but with public keys I'll need to keep several dozens
of .gnupg directories
Hi!
On Mon, Mar 08, 2010 at 01:06:06PM +0100, Werner Koch wrote:
FWIW, You should use public key encryption instead of symmetric only
encryption. This makes everything much easier.
I don't think so. Every project encrypt it backups with different
passwords (needed for security), and right now
On Mon, 8 Mar 2010 01:43, power...@powerman.name said:
I've a lot of projects (each has separate user account) which use gpg for
encrypting daily backups (from cron) in this way:
gpg --batch --cipher-algo AES256 -c --passphrase-file PASSFILE BACKUP.tar
FWIW, You should use public key
Hi!
Looks like we need an option to suppress warning about gpg-agent.
Long story:
I've a lot of projects (each has separate user account) which use gpg for
encrypting daily backups (from cron) in this way:
gpg --batch --cipher-algo AES256 -c --passphrase-file PASSFILE BACKUP.tar
The
