key expired

Gregg Reynolds

unread,

Jan 14, 2019, 12:51:40 PM1/14/19

to bazel-discuss

FYI, on mac os:

$ gpg --verify bazel-0.21.0-installer-darwin-x86_64.sh.sig

gpg: assuming signed data in 'bazel-0.21.0-installer-darwin-x86_64.sh'

gpg: Signature made Wed Dec 19 07:58:19 2018 CST

gpg: using RSA key 71A1D0EFCFEB6281FD0437C93D5919B448457EE0

gpg: Good signature from "Bazel Developer (Bazel APT repository key) <baze...@googlegroups.com>" [expired]

gpg: Note: This key has expired!

László Csomor

unread,

Jan 15, 2019, 3:04:24 AM1/15/19

to Gregg Reynolds, bazel-discuss, Klaus Aehlig

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAO40MinYy0adNVWjJGLXUoVc%3D0miZsswpgx1FcRqV7jxGNY_Vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Klaus Aehlig

unread,

Jan 15, 2019, 5:11:30 AM1/15/19

to László Csomor, Gregg Reynolds, bazel-discuss

> +Klaus Aehlig <aeh...@google.com>

I do not have access to that key---by design. The key is stored
on somewhere our release pipeline; so someone with direct access
there will have to extend the expiry date.

--
Klaus Aehlig
Google Germany GmbH, Erika-Mann-Str. 33, 80636 Muenchen

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg

Geschaeftsfuehrer: Paul Terence Manicle, Halimah DeLaine Prado

László Csomor

unread,

Jan 15, 2019, 5:14:35 AM1/15/19

to Klaus Aehlig, Gregg Reynolds, bazel-discuss

Thanks for clarifying that Klaus.

Do you know who has access or where to find out who that is? If we knew the owner, do you know how they can extend the expiry date?

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

Philipp Wollermann

unread,

Jan 15, 2019, 5:44:29 AM1/15/19

to László Csomor, Klaus Aehlig, Gregg Reynolds, bazel-discuss

I guess I have the permissions, but I don't have the knowledge ;)

How do I extend the expiry date of the key? I mean, I can google it,
but I don't want to do something horribly wrong with our crypto stuff
or cause fingerprint mismatches by modifying our key somehow.

> --
> You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAJ5fxHJ_XSogUkuhVb589E4HfEMfxVDm_aKPErESzEfP0rYdog%40mail.gmail.com.

> For more options, visit https://groups.google.com/d/optout.

--
Philipp Wollermann
Software Engineer
phi...@google.com

Google Germany GmbH
Erika-Mann-Straße 33
80636 München

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise
erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes
weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich
bitte wissen, dass die E-Mail an die falsche Person gesendet wurde.

This e-mail is confidential. If you received this communication by
mistake, please don't forward it to anyone else, please erase all
copies and attachments, and please let me know that it has gone to the
wrong person.

Philipp Wollermann

unread,

Jan 15, 2019, 8:18:54 AM1/15/19

to Gregg Reynolds, bazel-discuss

Hi Gregg,

I checked this with Klaus and it looks like we extended the expiration
of the key in May 2018. The current key is valid until May 2020:

philwo@philwo-imacpro ~/release-key/test gpg --list-key
/Users/philwo/.gnupg/pubring.kbx
--------------------------------
pub rsa4096 2016-05-24 [SC] [expires: 2020-05-23]
71A1D0EFCFEB6281FD0437C93D5919B448457EE0
uid [ unknown] Bazel Developer (Bazel APT repository key)
<baze...@googlegroups.com>
sub rsa4096 2016-05-24 [E] [expires: 2020-05-23]

Can you try reimporting the key from our website or any keyserver?

Cheers,
Philipp

On Mon, Jan 14, 2019 at 6:51 PM Gregg Reynolds <d...@mobileink.com> wrote:
>

> --
> You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAO40MinYy0adNVWjJGLXUoVc%3D0miZsswpgx1FcRqV7jxGNY_Vw%40mail.gmail.com.

Gregg Reynolds

unread,

Jan 24, 2019, 11:42:41 AM1/24/19

to Philipp Wollermann, bazel-discuss

On Tue, Jan 15, 2019 at 7:18 AM Philipp Wollermann <phi...@google.com> wrote:

Hi Gregg,

I checked this with Klaus and it looks like we extended the expiration
of the key in May 2018. The current key is valid until May 2020:

philwo@philwo-imacpro ~/release-key/test gpg --list-key
/Users/philwo/.gnupg/pubring.kbx
--------------------------------
pub rsa4096 2016-05-24 [SC] [expires: 2020-05-23]
71A1D0EFCFEB6281FD0437C93D5919B448457EE0
uid [ unknown] Bazel Developer (Bazel APT repository key)
<baze...@googlegroups.com>
sub rsa4096 2016-05-24 [E] [expires: 2020-05-23]

Can you try reimporting the key from our website or any keyserver?

Thanks, looks good. FWIW, since some of us had the expired key in our keychain and didn't think to try re-importing it, you might want to add a note somewhere indicating that is what you should do if you get an "expired key" result.

Gregg

Reply all

Reply to author

Forward