Red Hat Bugzilla – Bug 1275094
Registering signing key cuts out leading zero
Last modified: 2016-12-20 10:09:19 EST
Description of problem: signing key with leading zero gets cut out the leading zero when importing using mokutil. Signing a custom module with the key and inserting module will produce 'Required key not available' error.
Steps to Reproduce:
1. import signing key starting with 00 to the system using mokutil
2. sign the custom module and insert module
Actual results: can't insert module with 'Required key not available' error
Expected results: importing signing key should include leading zero.
Created attachment 1086286 [details]
Screenshot of modinfo and system keyring
The custom module was signed with the signing key with leading zero. The system keyring shows both signing keys with/without the leading zero.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.