English Persian
Do not use rmmod directly!
During boot, the kernel loads X.509 keys into the system key ring or the system black list key ring from a set of persistent key stores as shown in xref:Working_with_Kernel_Modules.adoc#table-sources-for-system-key-rings[Sources For System Key Rings]
Each `parm` field presents one module parameter in the form `pass:attributes[{blank}]_parameter_name_:pass:attributes[{blank}]_description_pass:attributes[{blank}]`, where:
Each row of [command]#lsmod# output specifies:
Enrolling Public Key on Target System
Enroll your public key on all systems where you want to authenticate and load your kernel module.
`ethtool(8)` — The manual page for the [command]#ethtool# command.
====== Executable Key Enrollment Image Adding Public Key
====== Factory Firmware Image Including Public Key
Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can be installed and run on systems where UEFI Secure Boot is enabled. footnote:[Fedora does not require the use of Secure Boot on UEFI systems.] When Secure Boot is enabled, the EFI operating system boot loaders, the Fedora kernel, and all kernel modules must be signed with a private key and authenticated with the corresponding public key. The Fedora distribution includes signed boot loaders, signed kernels, and signed kernel modules. In addition, the signed first-stage boot loader and the signed kernel include embedded Fedora public keys. These signed executable binaries and embedded keys enable Fedora to install, boot, and run with the Microsoft UEFI Secure Boot CA keys that are provided by the UEFI firmware on systems that support UEFI Secure Boot.footnote:[Not all UEFI-based systems include support for Secure Boot.]
First, ensure the module is not already loaded into the kernel:
Follow these steps to add your public key to the MOK list:
For example, if you want to unload the `firewire_ohci` module, your terminal session might look similar to this:
For more information on installing packages with DNF, see xref:../package-management/DNF.adoc#sec-Installing[Installing Packages].
For more information on kernel modules and their utilities, see the following resources.
Generating a Public and Private X.509 Key Pair
Here are descriptions of a few of the fields in [command]#modinfo# output:
Here are the recommended steps for setting custom parameters and then loading a kernel module. This procedure illustrates the steps using the `e1000e` module, which is the network driver for Intel PRO/1000 network adapters, as an example:
However, this command will fail if a process is using: