[logback-dev] [JIRA] Updates for LOGBACK-1643: gpg key without user id; can't verify logback-classic-1.2.11.pom

[QOS.CH (JIRA)]

logback / LOGBACK-1643 [Open]
gpg key without user id; can't verify logback-classic-1.2.11.pom

==============================

Here's what changed in this issue in the last few minutes.
This issue has been created
This issue is now assigned to you.

View or comment on issue using this link
https://jira.qos.ch/browse/LOGBACK-1643

==============================
 Issue created
------------------------------

Jeff Gaston created this issue on 07/Jun/22 10:04 PM
Summary:              gpg key without user id; can't verify logback-classic-1.2.11.pom
Issue Type:           Bug
Affects Versions:     1.2.11
Assignee:             Logback dev list
Attachments:          logback-classic-1.2.11.pom, logback-classic-1.2.11.pom.asc, verification-keyring.keys
Created:              07/Jun/22 10:04 PM
Environment:          Ubuntu
Priority:             Major
Reporter:             Jeff Gaston
Description:
  We're observing that logback-classic-1.2.11.pom doesn't pass gpg verification (or [Gradle verification|https://github.com/gradle/gradle/issues/20958] ) 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
  
  /tmp $ 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
  
  ```
  
   
  
   
  
   


==============================
 This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)