Hide Forgot
Description of problem: FIPS *hmac* clutter up /boot. Even old files for kernels which have been removed are in the directory. /boot$ ls -lrt .vmlin*hmac* -rw-r--r-- 1 root root 166 Jan 25 08:49 .vmlinuz.hmac-4.3.4-300.fc23.x86_64 -rw-r--r-- 1 root root 166 Feb 26 13:52 .vmlinuz.hmac-4.4.3-300.fc23.x86_64 -rw-r--r-- 1 root root 166 Mar 4 12:53 .vmlinuz.hmac-4.4.4-301.fc23.x86_64 -rw-r--r-- 1 root root 166 Mar 10 13:05 .vmlinuz.hmac-4.4.5-300.fc23.x86_64 -rw-r--r-- 1 root root 166 Mar 16 18:19 .vmlinuz.hmac-4.4.6-300.fc23.x86_64 Version-Release number of selected component (if applicable): How reproducible: Install a new kernel. The default number of kernels to keep is 3 but more than that number will appear with each successive kernel install. Steps to Reproduce: 1. 2. 3. Actual results: Old kernels are removed, but old hmac files are not. Expected results: Old hmac files are removed. Additional info: Ultimately I would rather these files not get created at all. I am not sure what component is responsible for creating them, but am starting with dnf and various plugins and/or python scripts, which do the work of installing and deleting kernels. I see the 'fipscheck' package was installed 11/15/2015, and it contains program 'fipshmac' to generate hmac files. I assume does the postinstall work to remove old kernels.
%postun scriplets of kernel package should take care of them.
(In reply to Jan Silhan from comment #1) > %postun scriplets of kernel package should take care of them. That's not correct. The kernel installs these files to /lib/modules/<version>/ and the kernel-install script copies them to /boot as it does with the vmlinuz files themselves. kernel-install needs to remove these files on remove. Reassigning to systemd.
"The kernel installs these files to /lib/modules/<version>/..." Just curious - when you 'kernel installs' does that mean the scriptlet(s) for a particular kernel package create the files? How does 'kernel-install' get invoked? Is it from a scriptlet?
(In reply to Dominique Brazziel from comment #3) > "The kernel installs these files to /lib/modules/<version>/..." > > Just curious - when you 'kernel installs' does that mean the scriptlet(s) > for a particular kernel package create the files? No. They're produced as part of the RPM build and RPM installs them. > How does 'kernel-install' get invoked? Is it from a scriptlet? Yes. The %post scriptlet calls kernel-install to create the initramfs.
*** Bug 1369587 has been marked as a duplicate of this bug. ***
These files can be removed manually without problems for non-existent kernels, right?
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' of '23'. 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.
Problem still exists in Fedora 25. Where do we go from here? George...
(In reply to George R. Goffe from comment #8) > Problem still exists in Fedora 25. > Where do we go from here? Package maintainer can bump the version, or guess you can file another bug report.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.