Page MenuHome GnuPG

Public key block with Signature Key generates expired NIIBE Yutaka (GnuPG Release Key)
Closed, ResolvedPublic

Description

MS Windows version 10.0.19043 Build 19043

Steps to reproduce:

  1. Install Gpg4win from https://gpg4win.org/get-gpg4win.html with Kleopatra key manager
  2. On Signature Key webpage (https://gnupg.org/signature_key.html) copy public key block to clipboard
  3. Paste from clipboard into manually created key.pub file.
  4. Import key.pub into Kleopatra

It will generate 4 keys as described on Signature Key webpage, with correct uids, Key fingerprints, but one wrong expiration date for NIIBE Yutaka (GnuPG Release Key).

See screenshot at external link.

Details

External Link
https://imgur.com/Qn802OE
Version
10.0.19043 Build 19043

Event Timeline

DC0 changed External Link from https://gnupg.org/signature_key.html to https://imgur.com/Qn802OE.
werner claimed this task.
werner edited projects, added Support, www.gnupg.org; removed Bug Report.
werner added subscribers: gniibe, werner.

Well, the keys are not generated but public keys are imported. @gniibe's key has meanwhile expired but we keep it because it will allow users to verify some older source packages. An expired signature key is not an error but merely means that one should evaluate the meaning of the signature with more diligence.

(There are some peculiarities with his token based keys why there is no new key yet.)dev.gn