public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mario Barcala <barcala@nlpgo.com>
To: cygwin@cygwin.com
Subject: duplicity/gpg secret key error
Date: Tue, 07 Jun 2016 16:59:00 -0000	[thread overview]
Message-ID: <20160607165928.GA11087@nlpgo.com> (raw)

Hi all:

We are trying to configure duplicity to make backups of a Windows 7
machine (32 bit) and we get the following error:

> $ duplicity full --encrypt-key=6F84684A /cygdrive/c/Documents\ and\
> Settings scp://user@ip/directory
> Synchronizing remote metadata to local cache...
> GnuPG passphrase:
> Copying duplicity-full-signatures.20160421T110618Z.sigtar.gpg to local
> cache.
> Cleanup of temporary directory /tmp/duplicity-0QQxWE-tempdir failed - this
> is probably a bug.
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: encrypted with RSA key, ID 65A86B7F
> gpg: decryption failed: secret key not available
> ===== End GnuPG log =====

Notice that gpg key ID 65A86B7F is different from the one specified by
us 6F84684A. We have tried to use symetric encryption (removing
--encrypt-key=6F84684A), and even to specify --no-encryption, but the
error keeps the same.

We have reinstalled cygwin in a clean Windows machine and the error
arise the same (with the same RSA key id: 65A86B7F).

Any idea about the problem?

Any help will be appreciated.

Thank you,

  Mario Barcala

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2016-06-07 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 16:59 Mario Barcala [this message]
2016-06-09 10:55 ` Mario Barcala
2016-06-10 10:02   ` Mario Barcala
2016-06-10 15:38     ` duplicity/gpg secret key error (solved) Mario Barcala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160607165928.GA11087@nlpgo.com \
    --to=barcala@nlpgo.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).