English Persian
You will be asked to enter and confirm a password for this MOK enrollment request.
You should now be able to load your kernel module successfully.
Your kernel module is now ready for loading. Note that your signed kernel module is also loadable on systems where UEFI Secure Boot is disabled or on a non-UEFI system. That means you do not need to provide both a signed and unsigned version of your kernel module.
Your kernel module is in ELF image format and this script computes and appends the signature directly to the ELF image in your `my_module.ko` file. The [command]#modinfo# utility can be used to display information about the kernel module's signature, if it is present. For information on using the utility, see xref:Working_with_Kernel_Modules.adoc#sec-Displaying_Information_About_a_Module[Displaying Information About a Module].
You need to generate a public and private X.509 key pair that will be used to sign a kernel module after it has been built. The corresponding public key will be used to authenticate the kernel module when it is loaded.
You have figured out the dependency tree (which does not branch in this example) for the loaded Firewire modules: `firewire_ohci` depends on `firewire_core`, which itself depends on `crc-itu-t`.
You can use the [option]`-v` (or [option]`--verbose`) option to cause [command]#modprobe# to display detailed information about what it is doing, which can include loading module dependencies.
You can use [command]#modprobe# to load a kernel module with custom parameters using the following command line format:
You can unload `firewire_ohci` using the [command]#modprobe -v -r _module_name_pass:attributes[{blank}]# command, where [option]`-r` is short for [option]`--remove` and [option]`-v` for [option]`--verbose`:
You can unload all dependencies of the module you want to set parameters for, unload the module using [command]#modprobe -r#, and then load it with [command]#modprobe# along with a list of customized parameters. This method is often used when the module does not have many dependencies, or to test different combinations of parameters without making them persistent, and is the method covered in this section.
You can load the `Fibre Channel over Ethernet` module verbosely by typing the following at a shell prompt:
You can list all parameters that the module supports by using the [option]`-p` option. However, because useful value type information is omitted from [command]#modinfo -p# output, it is more useful to run:
You can enter multiple parameters and values by separating them with spaces.
You can display information about the keys on the system key rings using the [command]#keyctl# utility. The following is abbreviated example output from a Fedora system where UEFI Secure Boot is not enabled.
Working with Kernel Modules
When loading a module with custom parameters on the command line, be aware of the following:
When Fedora boots on a UEFI-based system with Secure Boot enabled, all keys that are in the Secure Boot db key database, but not in the dbx database of revoked keys, are loaded onto the system keyring by the kernel. The system keyring is used to authenticate kernel modules.
When entering the name of a kernel module as an argument to one of the [application]*kmod* utilities, do not append a `.ko` extension to the end of the name. Kernel module names do not have extensions; their corresponding files do.
use the user-space [application]*kmod* utilities to display, query, load and unload kernel modules and their dependencies;
Unloading a Module