On 22.08.2011 22:37,
address@hidden wrote:
> please stick to this workaround for now. my patch for reusing passphrase as sign passphrase (if the key to sign is also an encryption key)
>
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/revision/767
> has a bug that you discovered.
> hopefully the next version will have that fixed. will upload a branch for that.
>
> thanks ede/
duply.net
>
>
> On 22.08.2011 19:26, mogliii wrote:
>> When using SIGN_PASSPHRASE I get:
>>
>> These may be deleted by running duplicity with the "cleanup" command.
>> Reuse already set SIGNING_PASSPHRASE as PASSPHRASE
>>
>> And the backup succeeds without further interaction
>>
>> Mogliii
>>
>> On 22/08/2011 11:11,
address@hidden wrote:
>>> On
21.08.2011 23:36, Mogliii wrote:
>>>> Hi,
>>>>
>>>> Running duplicity 0.6.15 on ubuntu 10.04 in conjuncture with duply
>>>> (latest development version from 21stAugust).
>>>> I am trying to do a backup encrypted against two public keys and sign
>>>> with a private key. When I run the command I get this:
>>>>
>>>>
>>>> [snip]
>>>> -----------------
>>>> Connecting with backend: FTPBackend
>>>> Archive dir: /root/.cache/duplicity/duply_vserver
>>>>
>>>> Found 0 secondary backup chains.
>>>>
>>>> Found primary backup chain with matching signature chain:
>>>> -------------------------
>>>> Chain start time: Sun Aug 21 23:08:42 2011
>>>> Chain end time: Sun Aug 21 23:10:03 2011
>>>> Number of contained backup sets: 2
>>>> Total number of contained volumes: 2
>>>> Type of backup set: Time: Num volumes:
>>>> Full Sun Aug 21 23:08:42 2011 1
>>>> Incremental Sun Aug 21 23:10:03 2011 1
>>>> -------------------------
>>>> No orphaned or incomplete backup sets found.
>>>> PASSPHRASE variable not set, asking user.
>>>> GnuPG passphrase for signing key:
>>>>
>>> Seems to be a bug in the passphrase delivering code. That is quite new, so there could be bugs. Please try to set SIGN_PASSPHRASE to explicitely deliver a signing passphrase and see if that helps. I will doublecheck if i can reproduce the problem.
>>>
>>>> (I entered the passphrase twice by hand, thats why there are two
>>>> backups. Another odd thing is that gpg ask to repeat the passphrase. But
>>>> this does not make sense, I don't have to enter a passphrase twice to
>>>> log-in to eg. ssh...)
>>> This is a feature, although I already voted against it. Signing passphrases are asked two times and compared to ensure that they are correct and duplicity does not have to be restarted.
>>>
>>> @Ken: We have two people not understanding the need for a double input plus me.. Could we convert it to a one timer now. Please?
>>>
>>>> I believe this is a duplicity problem as the generated command follows
>>>> the man-page. Also: before signing duplicity had already access to the
>>>> ftp (so it could check that everything is up to date), for which it
>>>> requires the FTP_PASSWORD variable.
>>>>
>>> What locale is your system running on?
>>>
>>> ..ede/
duply.net
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>>
address@hidden
>>>
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>>
address@hidden
>>
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
> _______________________________________________
> Duplicity-talk mailing list
>
address@hidden
>
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk