On Tue, Oct 29, 2019 at 05:58:13PM -0400, Cleber Rosa wrote:
> On Tue, Oct 29, 2019 at 05:51:28PM -0400, Cleber Rosa wrote:
> > On Tue, Oct 29, 2019 at 09:13:45PM +0000, Peter Maydell wrote:
> > > On Mon, 28 Oct 2019 at 23:50, Cleber Rosa <crosa@redhat.com> wrote:
> > > >
> > > > The following changes since commit aaffb853359829a37daaf883c773e8320b55c723:
> > > >
> > > > Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-10-28' into staging (2019-10-28 14:40:01 +0000)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > > git://github.com/clebergnu/qemu.git tags/python-next-pull-request
> > > >
> > > > for you to fetch changes up to efdb45bfd72745038909dfd1e970a827cb8d5d7e:
> > > >
> > > > tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu (2019-10-28 19:04:04 -0400)
> > > >
> > > > ----------------------------------------------------------------
> > >
> > > Hi; unless my scripts are driving gpg wrong, this seems to
> > > have been signed with an expired gpg key:
> > >
> > > gpg: Signature made Mon 28 Oct 2019 23:43:11 GMT
> > > gpg: using RSA key 7ABB96EB8B46B94D5E0FE9BB657E8D33A5F209F3
> > > gpg: Good signature from "Cleber Rosa <crosa@redhat.com>" [expired]
> > > gpg: Note: This key has expired!
> > > Primary key fingerprint: 7ABB 96EB 8B46 B94D 5E0F E9BB 657E 8D33 A5F2 09F3
> > >
> > >
> > > thanks
> > > -- PMM
> >
> > Hi Peter,
> >
> > Nothing wrong with your scripts. I updated my key about a week ago,
> > but I'm almost certain that the key servers that I sent it to was
> > acting funky.
> >
> > After some further pushes, I see it on:
> >
> > http://keys.gnupg.net/pks/lookup?op=vindex&fingerprint=on&search=0x657E8D33A5F209F3
> >
> > ---
> >
> > Search results for '0x657e8d33a5f209f3'
> > Type bits/keyID cr. time exp time key expir
> > pub 4096R/A5F209F3 2014-10-16
> > Fingerprint=7ABB 96EB 8B46 B94D 5E0F E9BB 657E 8D33 A5F2 09F3
> >
> > uid Cleber Rosa <crosa@redhat.com>
> > sig sig3 A5F209F3 2014-10-16 __________ 2019-10-15 [selfsig]
> > sig sig 7657B59A 2014-10-16 __________ __________ Rudá Moura <rmoura@redhat.com>
> > sig sig 2527436A 2019-03-05 __________ __________ Eric Blake <eblake@redhat.com>
> > sig sig 984DC5A6 2019-03-06 __________ __________ Eduardo Habkost <ehabkost@redhat.com>
> > sig sig3 96799EF4 2019-03-06 __________ __________ Bandan Das <bsd@redhat.com>
> > sig sig3 A5F209F3 2019-10-22 __________ 2024-10-20 [selfsig]
> >
> > sub 4096R/5B75AD33 2014-10-16
> > sig sbind A5F209F3 2014-10-16 __________ 2019-10-15 []
> > sig sbind A5F209F3 2019-10-22 __________ 2024-10-20 []
> >
> > ---
> >
> > And with a fresh environment:
> >
> > $ podman run --rm -ti fedora:30
> > [root@afba6c046a22 /]# gpg --search-key 657E8D33A5F209F3
> > gpg: directory '/root/.gnupg' created
> > gpg: keybox '/root/.gnupg/pubring.kbx' created
> > gpg: data source: https://51.38.91.189:443
> > (1) Cleber Rosa <crosa@redhat.com>
> > 4096 bit RSA key 657E8D33A5F209F3, created: 2014-10-16, expires: 2024-10-20
> > Keys 1-1 of 1 for "657E8D33A5F209F3". Enter number(s), N)ext, or Q)uit > 1
> > gpg: key 657E8D33A5F209F3: 4 signatures not checked due to missing keys
> > gpg: /root/.gnupg/trustdb.gpg: trustdb created
> > gpg: key 657E8D33A5F209F3: public key "Cleber Rosa <crosa@redhat.com>" imported
> > gpg: no ultimately trusted keys found
> > gpg: Total number processed: 1
> > gpg: imported: 1
> >
> > ---
> >
> > So I guess "all" you'd need is a refresh. Sorry for the inconvenience,
> > and let me know if there's anything else I can do.
> >
> > - Cleber.
>
> OK, so now I don't see the updated key anymore on the public key servers,
> which confirms that I'm doing something wrong.
>
> I'm trying to fix that situation. Sorry for the inconvenience again.
>
> - Cleber.
I'm now getting the updated key on every single server I've tried.
Any further feedback/request is highly appreciated.
Thanks,
- Cleber.