Bug 2569338
| Summary: | libtpms: source signature does not verify with openpgpverify (SHA-1 key self-signatures) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jakub Jelen <jjelen> |
| Component: | libtpms | Assignee: | Stefan Berger <stefanb> |
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | davide, marcandre.lureau, stefanb |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2569052 | ||
|
Description
Jakub Jelen
2026-11-10 09:02:15 UTC
I now sent my updated self-signature with the following command and updated the signature v0.10.2.tar.gz.asc on the libtpms v0.10.2 release: gpg --keyserver hkps://keys.openpgp.org --send-keys B818B9CADF9089C2D5CEC66B75AD65802A0B4211 How far does this get us now? Hello, thank you for the prompt reply. With the updated key from keyserver and this signature, everything works just fine! Please, let me know if I should open a Fedora dist git PR for you, or you will take care of that. Given that the new signature file has the same name as the old one, I think the lookaside cache will not accept it so it will likely have to live in the dist git itself until the next release. (In reply to Jakub Jelen from comment #2) > Hello, thank you for the prompt reply. With the updated key from keyserver > and this signature, everything works just fine! > > Please, let me know if I should open a Fedora dist git PR for you, or you > will take care of that. Given that the new signature file has the same name > as the old one, I think the lookaside cache will not accept it so it will > likely have to live in the dist git itself until the next release. Sure, please do. Thanks. |