Control: tag -1 + upstream
Control: severity -1 wishlist
Control: retitle -1 [duplicity] please support different passphrases for
signing and encryption
Hi Dominik,
Dominik George wrote (11 Oct 2013 23:44:46 GMT) :
When using different encryption and signing keys, the password
config variable
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
Dominik George wrote (12 Oct 2013 08:58:11 GMT) :
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!
I am glad this works fine for you. It wasn't the
Hi,
Anyway, we're digressing wrt. the topic of this bug, and I would
happily review a patch adding support for SIGN_PASSPHRASE.
I think you might have found it already ;).
However, I am absolutely certain this bug is not wishlist. I reset it to
normal, although I am tempted to say it is
Control: severity -1 wishlist
Hi,
I think you might have found it already ;).
Good.
However, I am absolutely certain this bug is not wishlist. I reset it to
normal, although I am tempted to say it is important.
I'm sorry, but that's not your call.
FYI, in my experience, reverting
Package: backupninja
Version: 1.0.1-1
Severity: normal
When using different encryption and signing keys, the password
config variable is not passed as PASSPHRASE environment variable,
making duplicity expect the passphrase on stdin. This is very
annoying because automatic backp runs are not
6 matches
Mail list logo
