Bug 1719930
Summary: | Custom kernels signed by locally produced keys using pesign are not recognized by the boot process. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | stan <gryt2> |
Component: | pesign | Assignee: | Peter Jones <pjones> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | gryt2, mjg59, pjones |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-12 18:38:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
stan
2019-06-12 18:07:43 UTC
Solved. I had thought that the public key for Red Hat must be included in the key ring, since the binary was signed with it. But, when I removed the Red Hat certificate from my binary, it booted just fine in UEFI secure boot. So, everything is working as designed, I just missed a step of the process. pesign --force -r -u 0 -i vmlinuz-5.2.0-0.rc4.git0.1.20190610.fc31.x86_64 -o vmlinuz-5.2.0-0.rc4.git0.1.20190610.fc31.x86_64.unsigned Closing as notabug. |