Uploaded image for project: 'Community Package Repository'
  1. Community Package Repository
  2. CPR-347

Nightlies GPG public key file outdated and expired

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2017/08/02
    • Labels:
      None
    • Environment:

      Debian

    • Template:
    • Sub-team:
    • Story Points:
      2
    • Sprint:
      RE 2016-05-25

      Description

      The copy of the GPG key at http://nightlies.puppetlabs.com/07BB6C57 has expired and should be refreshed with the current public key.

      The key expiry was extended in CPR-295 and seems to be available from the MIT keyserver with an expiry of 2019-02-11, but the key on the site expired on 2016-02-06:
      {{
      $ curl http://nightlies.puppetlabs.com/07BB6C57 | gpg --import
      % Total % Received % Xferd Average Speed Time Time Time Current
      Dload Upload Total Spent Left Speed
      100 5567 100 5567 0 0 21846 0 -::- -::- -::- 21831
      gpg: key 07BB6C57: public key "Puppet Labs Nightly Build Key (Puppet Labs Nightly Build Key) <delivery@puppetlabs.com>" imported
      gpg: Total number processed: 1
      gpg: imported: 1 (RSA: 1)
      gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
      gpg: depth: 0 valid: 1 signed: 15 trust: 0-, 0q, 0n, 0m, 0f, 1u
      gpg: depth: 1 valid: 15 signed: 5 trust: 15-, 0q, 0n, 0m, 0f, 0u
      gpg: next trustdb check due at 2016-06-25
      $ gpg -k 07BB6C57
      pub 4096R/07BB6C57 2013-02-06 [expired: 2016-02-06]
      uid Puppet Labs Nightly Build Key (Puppet Labs Nightly Build Key) <delivery@puppetlabs.com>
      uid Puppet Labs Nightly Build Key (Puppet Labs Nightly Build Key) <info@puppetlabs.com>}}

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ryan.mckern Ryan McKern
              Reporter:
              domcleal Dominic Cleal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support