> > I think there might be some confusion between signing and encrpyting > > anyway, because the config file commentary suggests that a pass- > > phrase is used for unlocking the encryption key, which is plain non- > > sense as GPG always uses public keys for (message) encryption. > > I don't think this to be non-sense. The passphrase that unlocks the > encryption key is needed at incremental backup time because duplicity > needs to decrypt the metadata of previous backup sets, in order to > know what's new to backup. If you still think it's non-sense while > being aware of this, please clarify :)
I am doing incremental backups without even having the encryption key private aprt available, I am encrypting backups to my smartcard which the server does not have access to. Works perfectly! -- Wer den Grünkohl nicht ehrt, ist der Mettwurst nicht wert! PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
signature.asc
Description: Digital signature
