[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-tracker] [bug #24198] IOError: [Errno 32] Broken pipe
From: |
David Abrahams |
Subject: |
[Duplicity-tracker] [bug #24198] IOError: [Errno 32] Broken pipe |
Date: |
Wed, 18 Feb 2009 15:35:32 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020911 Ubuntu/8.10 (intrepid) Firefox/3.0.6 |
Follow-up Comment #8, bug #24198 (project duplicity):
If you use gpg --edit-key you must set the trust level to "5 - ultimately
trusted," or it won't work. Is that a distinct operation from signing the
encryption key? Signing sounds like it would be cleaner...
Hmm, no signing is different: http://www.debian.org/events/keysigning
However, I tried to set my trust level back to 'unknown' and then sign the
key:
============
# gpg --edit-key 0559398E
gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
gpg: checking the trustdb
gpg: no ultimately trusted keys found
pub 1024D/1513B6C6 created: 2009-02-16 expires: never usage: SC
trust: undefined validity: unknown
sub 2048g/0559398E created: 2009-02-16 expires: never usage: E
[ unknown] (1). Duplicity Backup (Secure) <address@hidden>
Command> sign
"Duplicity Backup (Secure) <address@hidden>" was already signed by
key 1513B6C6
Nothing to sign with key 1513B6C6
Command> quit
address@hidden:/home/dave/src/zfs-fuse# gpg --edit-key 1513B6C6
gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
pub 1024D/1513B6C6 created: 2009-02-16 expires: never usage: SC
trust: undefined validity: unknown
sub 2048g/0559398E created: 2009-02-16 expires: never usage: E
[ unknown] (1). Duplicity Backup (Secure) <address@hidden>
Command> sign
"Duplicity Backup (Secure) <address@hidden>" was already signed by
key 1513B6C6
Nothing to sign with key 1513B6C6
==============
So it appears that either setting the trust to ultimate *also* signed the
key, or it was signed all along and the instruction to sign the key is
insufficient. This should all be in some helpful duplicity guide rather than
a bug report, so please consider this a documentation bug.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?24198>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/