The "Bitcoin Core Release Signing Key" for v0.11.0+ shows up as expired #9797

The "Bitcoin Core Release Signing Key" for v0.11.0+ shows up as expired

Steps to reproduce

1. Clear gpg key ring
2. Download https://bitcoin.org/laanwj-releases.asc (linked on https://bitcoin.org/en/download as "Bitcoin Core Release Signing Key" for v0.11.0+)
3. gpg --import laanwj-releases.asc
4. gpg --list-keys

Expected behaviour

The downloaded and imported release signing key shows up as valid.

Actual behaviour

The downloaded and imported release signing key shows up as expired.

gpg --list-keys

pub   4096R/36C2E964 2015-06-24 [expired: 2017-02-13]
uid                  Wladimir J. van der Laan (Bitcoin Core binary release signing key) <laanwj@gmail.com>

extra information

gpg --version

gpg (GnuPG) 1.4.18

See this recent (just posted) message to the bitcoin-core-dev mailing list.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

If you run into errors while verifying the release, please refresh the
following keys from the keyservers. Their expiration date has been bumped
forward recently:

- - 0x74810B012346C9A6  Wladimir J. van der Laan
- - 0x90C8019E36C2E964  Wladimir J. van der Laan (Bitcoin Core binary release signing key)

- From the command line, this is done with:

    gpg --refresh-keys 0x74810B012346C9A6 0x90C8019E36C2E964

Wladimir


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCgAGBQJYqZZ/AAoJEHSBCwEjRsmmC6YIAM4LUM2LBkcqAaicnZJeXn/O
1eZqwNb0uEJaOK+zc7DdVjAZS8OMLo0nTmSxx2YuoBC8T3tNblfI9cAfTq5uGf3m
kTODIVHtBFqOILKuJMTI1arS83+lgL6C56+yGiQAyVyI5OVd2CZTqA6P04DcQNs0
JU9LLopFg4eIY4aT7PTAQWWlMSJe1/e8URNuWDrarouvLoykitIwg2wmnv1nSjV6
pa4e608K1cHyF0S+ZJxSggNrxFs5b0BpPOG46sf/7rMiFzr7iPw9aOYgH7RRJGlT
Dv6Bv5PODum8vHeLNAlXjtOe20aZz3vchYLUixnaEHODfTtub0SQsMlUAZAbYl8=
=VQzJ
-----END PGP SIGNATURE-----

See also: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1513