tags 888878 + unreproducible moreinfo severity 888878 normal thanks On Tue, 30 Jan 2018 21:14:57 +0100, Erwan David writes: >When trying to restore a signed backup, with -v 8 I get following >error >Volume was signed by key EE04D0D2B40F856F, not 0xEE04D0D2B40F856F
first, i'd recommend not passing any sign-key parameter to the restore call as that only makes it picky wrt missigned files. as far as i can tell the signature check does not result in termination of the restore job; a mismatched sig only causes an error message and a nonzero exit code, but the file restoration still happens normally. second, i cannot reproduce this with the current version of duplicity (0.7.16-1): backing up with --sign-key X --encrypt-key X results in a correctly encrypted and restorable archive, signed with and encrypted to a subkey of my key X. in order to perform any further diagnostics i need the actual output of a failed restore run with -v9. regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ Some people think I'm nice & are shocked when they find out different. I'm not a nice person, & I don't care about you. -- Linus @ lca2015
signature.asc
Description: Digital Signature
