On Wed, Nov 13, 2019, at 03:19, Alexander Zangerl wrote:
> On Tue, 12 Nov 2019 17:10:40 -0500, "Michael Terry" writes:
> >I could throw you a patch tomorrow. And it could have the benefit of
> >being upstreamable too.
>
> that sounds very good; thanks for your time!
OK, attached is a patch that I
On Tue, 12 Nov 2019 17:10:40 -0500, "Michael Terry" writes:
>I don’t suppose you’d object to an update to the patch that at least
>makes it conditional to gpg key scenarios?
absolutely no objection; i just hadn't found the time to add that clean logic
the last time i looked at that particular iss
On Tue, Nov 12, 2019, at 17:04, Alexander Zangerl wrote:
> On Tue, 12 Nov 2019 07:46:37 -0500, "Michael Terry" writes:
> >Wait, you mean that you want to back up without even needing the
> >passphrase for the secret gpg key?
>
> that's precisely it.
>
> the secret key isn't even present on the ma
On Tue, 12 Nov 2019 07:46:37 -0500, "Michael Terry" writes:
>Wait, you mean that you want to back up without even needing the
>passphrase for the secret gpg key?
that's precisely it.
the secret key isn't even present on the machines that the backup runs on,
just the public key. gpg (on duplicity'
On Tue, Nov 12, 2019, at 07:39, Michael Terry wrote:
> On Tue, Nov 12, 2019, at 04:54, Alexander Zangerl wrote:
>> >test the gpg encryption key issue (this one needs you to specify both
>> >KEY and PASSPHRASE environment variables -- your gpg key id and
>> >passphrase respectively).
>>
>> your sce
On Tue, Nov 12, 2019, at 04:54, Alexander Zangerl wrote:
> >test the gpg encryption key issue (this one needs you to specify both
> >KEY and PASSPHRASE environment variables -- your gpg key id and
> >passphrase respectively).
>
> your scenario doesn't cover the case i'm trying to keep working, ie.
On Mon, 11 Nov 2019 00:57:03 -0500, Michael Terry writes:
>But then duplicity fixed the issue with gpg encryption keys and Debian never
>dropped its patch.
i disagree with that assessment: the way i read validate_encryption_settings
in dup_main, resuming a backup with gpg encryption only (and no s
Package: duplicity
Version: 0.8.04-2ubuntu1
Severity: normal
Dear Maintainer,
Many years ago, duplicity had a bug that allowed you to resume a backup with a
different
password than the one with which you started the backup. This left your backup
chain
in an unrecoverable state, since duplicity
8 matches
Mail list logo
