Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-1643

gpg key without user id; can't verify logback-classic-1.2.11.pom

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 1.5.12
    • 1.2.11
    • None
    • None
    • Ubuntu

    Description

      We're observing that logback-classic-1.2.11.pom doesn't pass gpg verification (or Gradle verification ) and it seems to be because `gpg: key 2C7B12F2A511E325: new key but contains no user ID - skipped`

       

      See this output:

      ```

      $ gpg --verify logback-classic-1.2.11.pom.asc
      gpg: assuming signed data in 'logback-classic-1.2.11.pom'
      gpg: Signature made Sat 05 Mar 2022 04:14:24 PM EST
      gpg: using RSA key 2C7B12F2A511E325
      gpg: Can't check signature: No public key

      $ gpg --receive-keys 2C7B12F2A511E325
      gpg: key 2C7B12F2A511E325: new key but contains no user ID - skipped
      gpg: Total number processed: 1
      gpg: w/o user IDs: 1

      ```

       

       

       

      Attachments

        1. logback-classic-1.2.11.pom
          9 kB
          Jeff Gaston
        2. logback-classic-1.2.11.pom.asc
          0.4 kB
          Jeff Gaston
        3. verification-keyring.keys
          1 kB
          Jeff Gaston

        Activity

          People

            logback-dev Logback dev list
            mathjeff Jeff Gaston
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: