duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Duplicity without Secret Key


From: Colin Ryan
Subject: Re: [Duplicity-talk] Duplicity without Secret Key
Date: Sat, 04 Oct 2008 12:49:40 -0400
User-agent: Thunderbird 2.0.0.17 (Windows/20080914)

I'll note as well that straight gpg I did not need this option.

Colin Ryan wrote:
Kenneth,

Yes I agree with that, but since the OTHERHEX key is the first and only private key in the keyring of the userid running duplicity is it not odd that i have to specify it for duplicity? It would be much nicer from a scripting perspective to not have to have this additional piece of knowledge for the scripts to function.

C

Kenneth Loafman wrote:
No, the gpg manual implies that you had it set up correctly.
http://www.gnupg.org/gph/en/manual/r1365.html

...Ken

Colin Ryan wrote:
I seem to have gotten this to work but I needed to force the default-key
for pgp with the:::

--gpg-options="--default-key=<OTHER HEX>"

even tho this key is the first in the keyring...anyone have any ideas as
to why I had to do this.

Colin

Colin Ryan wrote:
Hrm,

My duplicity options are:

duplicity incr   --verbosity=6 --num-retries=50
--archive-dir='/opt/aa/service/nas/offsite/duplicity' --sign-key=<HEX> --encrypt-key=<HEX>

Where HEX is the key id for the key with just the public key installed
and signed.

I get:


gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt failed: secret key not available
gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt failed: secret key not available

But if I use a key with the private key available it seems to work.

As well, a basic sanity check of gpg with the offending key appears to
be fine.

gpg  -r <HEX> --sign --encrypt --debug 64 < /etc/hosts > test

Any ideas?




Colin Ryan wrote:
Ahh thanks I was using that cause it said then that the manifest etc
are unenrypted locally so I'll try fiddling some more.

Thanks folks

Andrew Kohlsmith (lists) wrote:
On October 3, 2008 10:12:47 am Kenneth Loafman wrote:
If you use --archive-dir=<localdir> then duplicity will not need to
decrypt the manifest and sig files and should not need the secret key.
I'm not sure this path has been tested, but it should work.
This exactly how I use it (I encrypt with several keys, only one of
which the duplicity server has the private key for), and it works
fine with --archive-dir.

-A.


_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk

_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk

_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk

_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk



------------------------------------------------------------------------

_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk



_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk





reply via email to

[Prev in Thread] Current Thread [Next in Thread]