From: John Snow <jsnow@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [qemu-web PATCH] Add signing pubkey for python-qemu-qmp package
Date: Tue, 23 Aug 2022 10:29:26 -0400 [thread overview]
Message-ID: <CAFn=p-ZDaxx978qHGTJnxYnja0hn8RF8d9fbnGYZtRO5GJO=-w@mail.gmail.com> (raw)
In-Reply-To: <CABJz62M8_197kahaNtBC1eSda5WJo6i7B1tsKF5+uMD+HXfj_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On Tue, Aug 23, 2022, 5:16 AM Andrea Bolognani <abologna@redhat.com> wrote:
> On Thu, Aug 18, 2022 at 12:53:58PM -0400, John Snow wrote:
> > Add the pubkey currently used for signing PyPI releases of qemu.qmp to a
> > stable location where it can be referenced by e.g. Fedora RPM specfiles.
> >
> > At present, the key happens to just simply be my own -- but future
> > releases may be signed by a different key. In that case, we can
> > increment '1.txt' to '2.txt' and so on. The old keys should be left in
> > place.
> >
> > The format for the keyfile was chosen by copying what OpenStack was
> > doing:
> >
> https://releases.openstack.org/_static/0x2426b928085a020d8a90d0d879ab7008d0896c8a.txt
> >
> > Generated with:
> > > gpg --with-fingerprint --list-keys jsnow@redhat.com > pubkey
> > > gpg --armor --export jsnow@redhat.com >> pubkey
>
> You might want to pass
>
> --export-options export-minimal
>
> to the second command in order to obtain a significantly smaller file
> that can still serve the intended purpose.
>
OK, I'll test with this option. Thanks!
((Doesn't know anything about gpg))
> --
> Andrea Bolognani / Red Hat / Virtualization
>
>
[-- Attachment #2: Type: text/html, Size: 2182 bytes --]
prev parent reply other threads:[~2022-08-23 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:53 [qemu-web PATCH] Add signing pubkey for python-qemu-qmp package John Snow
2022-08-19 16:21 ` Paolo Bonzini
2022-08-23 9:16 ` Andrea Bolognani
2022-08-23 14:29 ` John Snow [this message]
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='CAFn=p-ZDaxx978qHGTJnxYnja0hn8RF8d9fbnGYZtRO5GJO=-w@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=abologna@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 NNTP newsgroup(s).