Bug 99399 - [xorg-server] Signing key has expired
Summary: [xorg-server] Signing key has expired
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Release (show other bugs)
Version: unspecified
Hardware: Other All
: medium critical
Assignee: Adam Jackson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-13 14:30 UTC by Phil Wyett
Modified: 2018-08-10 21:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Phil Wyett 2017-01-13 14:30:15 UTC
[xorg-server] Signing key has expired.

1.19.1

gpg: assuming signed data in 'xorg-server-1.19.1.tar.gz'
gpg: Signature made Wed 11 Jan 2017 21:25:17 GMT
gpg:                using DSA key 5B8A2D50A0ECD0D3
gpg: Can't check signature: No public key

Verification on building on arch.

Key: DD38563A8A8224537D1F90E45B8A2D50A0ECD0D3

==> Verifying source file signatures with gpg...
xorg-server-1.19.1.tar.bz2 ... Passed (WARNING: the key has expired.)
==> WARNING: Warnings have occurred while verifying the signatures.
Please make sure you really trust them.

Import of key:

gpg --recv-keys 5B8A2D50A0ECD0D3
gpg: key 5B8A2D50A0ECD0D3: public key "Adam Jackson <ajax@benzedrine.nwnk.net>" imported
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Total number processed: 1
gpg:               imported: 1

List keys:

pub   dsa1024 2004-06-13 [SC] [expired: 2015-11-01]
      DD38563A8A8224537D1F90E45B8A2D50A0ECD0D3
uid           [ expired] Adam Jackson <ajax@benzedrine.nwnk.net>
uid           [ expired] Adam Jackson <ajax@nwnk.net>
uid           [ expired] Adam Jackson <ajax@redhat.com>
uid           [ expired] Adam Jackson <ajax@engr.sgi.com>
uid           [ expired] Adam Jackson <ajax@wildopensource.com>
Comment 1 Adam Jackson 2018-08-10 21:51:14 UTC
I've created a new one and deleted the old.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.