[Top][All Lists]

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

gnupload question

From: Eric Blake
Subject: gnupload question
Date: Wed, 21 Jul 2010 08:36:23 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100621 Fedora/3.0.5-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.3 Thunderbird/3.0.5

I'm in the interesting situation of trying to upload autoconf 2.67
signed by my new key, but while still waiting for my new key to be
installed by the ftp-upload folks to run the upload process (see
Right now, gnupload assumes that it should both create the .sig files,
as well as the signed upload .directive.asc file, using the same key.
But does the GNU upload process really require that the .sig and the
.directive.asc be created with the same key, or does it only validate
the directive, in which case I could manually create a .sig with my new
key but the .directive.asc with my old key?  While is
clear that an upload must be a triple, it is not clear whether the .sig
is validated.  If the split key approach works, should gnupload be given
an optional argument to allow a second key for creating the .sig,
different from the main key used for the .directive.asc, to save anyone
else the hassle of having to manually reproduce gnupload steps just to
get the split key behavior?

Of course, if the ftp-upload folks respond in time, this will be a moot
point for me, as I can just do the autoconf 2.67 upload with my new key.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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