delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:references | |
:mime-version:content-type:in-reply-to; q=dns; s=default; b=c+sP | |
lbH3V2AFAYy3pX1fE31+DqGDltGKuXLtUSUU7Nm5mTS9LrH7qfMWKHh8RZl3QQbw | |
KoJqB+B4QV2JDm9wndX0bdp3IDAXZtswnELyh6rGtnHGnvksPEEJl+7Y4LTCEM+3 | |
zRAObItLsuCT5/QrJcnDUEm+TeYmV8o8kL64VlQ= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:references | |
:mime-version:content-type:in-reply-to; s=default; bh=rb0omWestr | |
kjPNdzN7Z5tEk+Rpg=; b=WXudTkcAy9pVlhkgLhocBr34kJnTqYh3qcGIbrb7wG | |
ed0u3TinTXbFCuZrSkLO4WHoO1+mFl0D/6pA8H7HVUDs2rNg739yCRwPPTV9UsxQ | |
f1xZogx7xiwFHjG5+zU2UlEiYfBvXCbGN00gLAuerm0CIC46nT304OOLEyP4CuUV | |
I= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=-0.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=GnuPG, RSA, Ultimate, Settings |
X-HELO: | relay5-d.mail.gandi.net |
Date: | Fri, 10 Jun 2016 16:49:25 +0200 |
From: | Mario Barcala <barcala AT nlpgo DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: duplicity/gpg secret key error (solved) |
Message-ID: | <20160610144925.GA16040@nlpgo.com> |
References: | <20160607165928 DOT GA11087 AT nlpgo DOT com> <20160609105509 DOT GA14257 AT nlpgo DOT com> <20160610085725 DOT GA15668 AT nlpgo DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <20160610085725.GA15668@nlpgo.com> |
User-Agent: | Mutt/1.5.23 (2014-03-12) |
X-IsSubscribed: | yes |
The problem was to make our tests in different machines using the same server directory (and we forgot to clean it) and different GPG keys. We have removed .cache on local machine and server previous backed up files and all started to work fine. Regards, Mario Barcala Mario Barcala wrote: > The same error with the same GPG key id in a no virtualized Windows > 8.1 machine. > > Maybe it is a bug, as the message claims? > > Mario Barcala > > Mario Barcala wrote: > > Update: > > > > We have tried it with virtualized versions of Windows 7 Ultimate and > > Windows 8.1 (32 and 64 bits) and the error keeps the same, but we > > succeed with the same settings inside a no virtualized Windows 7 > > Ultimate. > > > > Is there any problem with virtualization? We don't know what to do > > from now. Tomorrow we'll test the same config inside a no virtualized > > Windows 8.1. > > > > Thank you, > > > > Mario Barcala > > > > Mario Barcala wrote: > > > 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 AT 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. > > > > -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |