sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget./translations/zh_CN/admin-guide/module-signingmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/zh_TW/admin-guide/module-signingmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/it_IT/admin-guide/module-signingmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/ja_JP/admin-guide/module-signingmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/ko_KR/admin-guide/module-signingmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/pt_BR/admin-guide/module-signingmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/sp_SP/admin-guide/module-signingmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhsection)}(hhh](htitle)}(hKernel module signing facilityh]hKernel module signing facility}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhH/var/lib/git/docbuild/linux/Documentation/admin-guide/module-signing.rsthKubhcomment)}(hCONTENTSh]hCONTENTS}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhhhhKubh)}(hhh]h}(h]h ]h"]h$]h&]hhuh1hhhhhhhhKubh)}(h - Overview.h]h - Overview.}hhsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhKubh)}(h- Configuring module signing.h]h- Configuring module signing.}hhsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhKubh)}(h- Generating signing keys.h]h- Generating signing keys.}hjsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhKubh)}(h- Public keys in the kernel.h]h- Public keys in the kernel.}hjsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhK ubh)}(h- Manually signing modules.h]h- Manually signing modules.}hjsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhK ubh)}(h- Signed modules and stripping.h]h- Signed modules and stripping.}hj,sbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhK ubh)}(h- Loading signed modules.h]h- Loading signed modules.}hj:sbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhK ubh)}(h,- Non-valid signatures and unsigned modules.h]h,- Non-valid signatures and unsigned modules.}hjHsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhK ubh)}(h+- Administering/protecting the private key.h]h+- Administering/protecting the private key.}hjVsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhKubh)}(hhh](h)}(hOverviewh]hOverview}(hjghhhNhNubah}(h]h ]h"]h$]h&]uh1hhjdhhhhhKubh paragraph)}(hXThe kernel module signing facility cryptographically signs modules during installation and then checks the signature upon loading the module. This allows increased kernel security by disallowing the loading of unsigned modules or modules signed with an invalid key. Module signing increases security by making it harder to load a malicious module into the kernel. The module signature checking is done by the kernel so that it is not necessary to have trusted userspace bits.h]hXThe kernel module signing facility cryptographically signs modules during installation and then checks the signature upon loading the module. This allows increased kernel security by disallowing the loading of unsigned modules or modules signed with an invalid key. Module signing increases security by making it harder to load a malicious module into the kernel. The module signature checking is done by the kernel so that it is not necessary to have trusted userspace bits.}(hjwhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKhjdhhubjv)}(hXcThis facility uses X.509 ITU-T standard certificates to encode the public keys involved. The signatures are not themselves encoded in any industrial standard type. The built-in facility currently only supports the RSA, NIST P-384 ECDSA and NIST FIPS-204 ML-DSA public key signing standards (though it is pluggable and permits others to be used). For RSA and ECDSA, the possible hash algorithms that can be used are SHA-2 and SHA-3 of sizes 256, 384, and 512 (the algorithm is selected by data in the signature); ML-DSA does its own hashing, but is allowed to be used with a SHA512 hash for signed attributes.h]hXcThis facility uses X.509 ITU-T standard certificates to encode the public keys involved. The signatures are not themselves encoded in any industrial standard type. The built-in facility currently only supports the RSA, NIST P-384 ECDSA and NIST FIPS-204 ML-DSA public key signing standards (though it is pluggable and permits others to be used). For RSA and ECDSA, the possible hash algorithms that can be used are SHA-2 and SHA-3 of sizes 256, 384, and 512 (the algorithm is selected by data in the signature); ML-DSA does its own hashing, but is allowed to be used with a SHA512 hash for signed attributes.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKhjdhhubeh}(h]overviewah ]h"]overviewah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hConfiguring module signingh]hConfiguring module signing}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK)ubjv)}(hThe module signing facility is enabled by going to the :menuselection:`Enable Loadable Module Support` section of the kernel configuration and turning on::h](h7The module signing facility is enabled by going to the }(hjhhhNhNubhinline)}(hEnable Loadable Module Supporth]hEnable Loadable Module Support}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtext/:menuselection:`Enable Loadable Module Support`uh1jhjubh4 section of the kernel configuration and turning on:}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhK+hjhhubh literal_block)}(h7CONFIG_MODULE_SIG "Module signature verification"h]h7CONFIG_MODULE_SIG "Module signature verification"}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhK/hjhhubjv)}(h'This has a number of options available:h]h'This has a number of options available:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhK1hjhhubh block_quote)}(hX (1) :menuselection:`Require modules to be validly signed` (``CONFIG_MODULE_SIG_FORCE``) This specifies how the kernel should deal with a module that has a signature for which the key is not known or a module that is unsigned. If this is off (ie. "permissive"), then modules for which the key is not available and modules that are unsigned are permitted, but the kernel will be marked as being tainted, and the concerned modules will be marked as tainted, shown with the character 'E'. If this is on (ie. "restrictive"), only modules that have a valid signature that can be verified by a public key in the kernel's possession will be loaded. All other modules will generate an error. Irrespective of the setting here, if the module has a signature block that cannot be parsed, it will be rejected out of hand. (2) :menuselection:`Automatically sign all modules` (``CONFIG_MODULE_SIG_ALL``) If this is on then modules will be automatically signed during the modules_install phase of a build. If this is off, then the modules must be signed manually using:: scripts/sign-file (3) :menuselection:`Which hash algorithm should modules be signed with?` This presents a choice of which hash algorithm the installation phase will sign the modules with: =============================== ========================================== ``CONFIG_MODULE_SIG_SHA256`` :menuselection:`Sign modules with SHA-256` ``CONFIG_MODULE_SIG_SHA384`` :menuselection:`Sign modules with SHA-384` ``CONFIG_MODULE_SIG_SHA512`` :menuselection:`Sign modules with SHA-512` ``CONFIG_MODULE_SIG_SHA3_256`` :menuselection:`Sign modules with SHA3-256` ``CONFIG_MODULE_SIG_SHA3_384`` :menuselection:`Sign modules with SHA3-384` ``CONFIG_MODULE_SIG_SHA3_512`` :menuselection:`Sign modules with SHA3-512` =============================== ========================================== The algorithm selected here will also be built into the kernel (rather than being a module) so that modules signed with that algorithm can have their signatures checked without causing a dependency loop. (4) :menuselection:`File name or PKCS#11 URI of module signing key` (``CONFIG_MODULE_SIG_KEY``) Setting this option to something other than its default of ``certs/signing_key.pem`` will disable the autogeneration of signing keys and allow the kernel modules to be signed with a key of your choosing. The string provided should identify a file containing both a private key and its corresponding X.509 certificate in PEM form, or — on systems where the OpenSSL ENGINE_pkcs11 is functional — a PKCS#11 URI as defined by RFC7512. In the latter case, the PKCS#11 URI should reference both a certificate and a private key. If the PEM file containing the private key is encrypted, or if the PKCS#11 token requires a PIN, this can be provided at build time by means of the ``KBUILD_SIGN_PIN`` variable. (5) :menuselection:`Additional X.509 keys for default system keyring` (``CONFIG_SYSTEM_TRUSTED_KEYS``) This option can be set to the filename of a PEM-encoded file containing additional certificates which will be included in the system keyring by default. h]henumerated_list)}(hhh](h list_item)}(hX+:menuselection:`Require modules to be validly signed` (``CONFIG_MODULE_SIG_FORCE``) This specifies how the kernel should deal with a module that has a signature for which the key is not known or a module that is unsigned. If this is off (ie. "permissive"), then modules for which the key is not available and modules that are unsigned are permitted, but the kernel will be marked as being tainted, and the concerned modules will be marked as tainted, shown with the character 'E'. If this is on (ie. "restrictive"), only modules that have a valid signature that can be verified by a public key in the kernel's possession will be loaded. All other modules will generate an error. Irrespective of the setting here, if the module has a signature block that cannot be parsed, it will be rejected out of hand. h](jv)}(hS:menuselection:`Require modules to be validly signed` (``CONFIG_MODULE_SIG_FORCE``)h](j)}(h$Require modules to be validly signedh]h$Require modules to be validly signed}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtext5:menuselection:`Require modules to be validly signed`uh1jhjubh (}(hjhhhNhNubhliteral)}(h``CONFIG_MODULE_SIG_FORCE``h]hCONFIG_MODULE_SIG_FORCE}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh)}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhK3hjubjv)}(hThis specifies how the kernel should deal with a module that has a signature for which the key is not known or a module that is unsigned.h]hThis specifies how the kernel should deal with a module that has a signature for which the key is not known or a module that is unsigned.}(hj3hhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhK6hjubjv)}(hXIf this is off (ie. "permissive"), then modules for which the key is not available and modules that are unsigned are permitted, but the kernel will be marked as being tainted, and the concerned modules will be marked as tainted, shown with the character 'E'.h]hX If this is off (ie. “permissive”), then modules for which the key is not available and modules that are unsigned are permitted, but the kernel will be marked as being tainted, and the concerned modules will be marked as tainted, shown with the character ‘E’.}(hjAhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhK9hjubjv)}(hIf this is on (ie. "restrictive"), only modules that have a valid signature that can be verified by a public key in the kernel's possession will be loaded. All other modules will generate an error.h]hIf this is on (ie. “restrictive”), only modules that have a valid signature that can be verified by a public key in the kernel’s possession will be loaded. All other modules will generate an error.}(hjOhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhK>hjubjv)}(h}Irrespective of the setting here, if the module has a signature block that cannot be parsed, it will be rejected out of hand.h]h}Irrespective of the setting here, if the module has a signature block that cannot be parsed, it will be rejected out of hand.}(hj]hhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKBhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hX :menuselection:`Automatically sign all modules` (``CONFIG_MODULE_SIG_ALL``) If this is on then modules will be automatically signed during the modules_install phase of a build. If this is off, then the modules must be signed manually using:: scripts/sign-file h](jv)}(hK:menuselection:`Automatically sign all modules` (``CONFIG_MODULE_SIG_ALL``)h](j)}(hAutomatically sign all modulesh]hAutomatically sign all modules}(hjyhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtext/:menuselection:`Automatically sign all modules`uh1jhjuubh (}(hjuhhhNhNubj)}(h``CONFIG_MODULE_SIG_ALL``h]hCONFIG_MODULE_SIG_ALL}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjuubh)}(hjuhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhKFhjqubjv)}(hIf this is on then modules will be automatically signed during the modules_install phase of a build. If this is off, then the modules must be signed manually using::h]hIf this is on then modules will be automatically signed during the modules_install phase of a build. If this is off, then the modules must be signed manually using:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKIhjqubj)}(hscripts/sign-fileh]hscripts/sign-file}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhKMhjqubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hX:menuselection:`Which hash algorithm should modules be signed with?` This presents a choice of which hash algorithm the installation phase will sign the modules with: =============================== ========================================== ``CONFIG_MODULE_SIG_SHA256`` :menuselection:`Sign modules with SHA-256` ``CONFIG_MODULE_SIG_SHA384`` :menuselection:`Sign modules with SHA-384` ``CONFIG_MODULE_SIG_SHA512`` :menuselection:`Sign modules with SHA-512` ``CONFIG_MODULE_SIG_SHA3_256`` :menuselection:`Sign modules with SHA3-256` ``CONFIG_MODULE_SIG_SHA3_384`` :menuselection:`Sign modules with SHA3-384` ``CONFIG_MODULE_SIG_SHA3_512`` :menuselection:`Sign modules with SHA3-512` =============================== ========================================== The algorithm selected here will also be built into the kernel (rather than being a module) so that modules signed with that algorithm can have their signatures checked without causing a dependency loop. h](jv)}(hD:menuselection:`Which hash algorithm should modules be signed with?`h]j)}(h3Which hash algorithm should modules be signed with?h]h3Which hash algorithm should modules be signed with?}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextjuh1jhjubah}(h]h ]h"]h$]h&]uh1juhhhKPhjubjv)}(haThis presents a choice of which hash algorithm the installation phase will sign the modules with:h]haThis presents a choice of which hash algorithm the installation phase will sign the modules with:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKRhjubj)}(hX[=============================== ========================================== ``CONFIG_MODULE_SIG_SHA256`` :menuselection:`Sign modules with SHA-256` ``CONFIG_MODULE_SIG_SHA384`` :menuselection:`Sign modules with SHA-384` ``CONFIG_MODULE_SIG_SHA512`` :menuselection:`Sign modules with SHA-512` ``CONFIG_MODULE_SIG_SHA3_256`` :menuselection:`Sign modules with SHA3-256` ``CONFIG_MODULE_SIG_SHA3_384`` :menuselection:`Sign modules with SHA3-384` ``CONFIG_MODULE_SIG_SHA3_512`` :menuselection:`Sign modules with SHA3-512` =============================== ========================================== h]htable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhjubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthK+uh1jhjubhtbody)}(hhh](hrow)}(hhh](hentry)}(hhh]jv)}(h``CONFIG_MODULE_SIG_SHA256``h]j)}(hj)h]hCONFIG_MODULE_SIG_SHA256}(hj+hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj'ubah}(h]h ]h"]h$]h&]uh1juhhhKVhj$ubah}(h]h ]h"]h$]h&]uh1j"hjubj#)}(hhh]jv)}(h*:menuselection:`Sign modules with SHA-256`h]j)}(hSign modules with SHA-256h]hSign modules with SHA-256}(hjKhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextjIuh1jhjGubah}(h]h ]h"]h$]h&]uh1juhhhKVhjDubah}(h]h ]h"]h$]h&]uh1j"hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j#)}(hhh]jv)}(h``CONFIG_MODULE_SIG_SHA384``h]j)}(hjuh]hCONFIG_MODULE_SIG_SHA384}(hjwhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjsubah}(h]h ]h"]h$]h&]uh1juhhhKWhjpubah}(h]h ]h"]h$]h&]uh1j"hjmubj#)}(hhh]jv)}(h*:menuselection:`Sign modules with SHA-384`h]j)}(hSign modules with SHA-384h]hSign modules with SHA-384}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextjuh1jhjubah}(h]h ]h"]h$]h&]uh1juhhhKWhjubah}(h]h ]h"]h$]h&]uh1j"hjmubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j#)}(hhh]jv)}(h``CONFIG_MODULE_SIG_SHA512``h]j)}(hjh]hCONFIG_MODULE_SIG_SHA512}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1juhhhKXhjubah}(h]h ]h"]h$]h&]uh1j"hjubj#)}(hhh]jv)}(h*:menuselection:`Sign modules with SHA-512`h]j)}(hSign modules with SHA-512h]hSign modules with SHA-512}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextjuh1jhjubah}(h]h ]h"]h$]h&]uh1juhhhKXhjubah}(h]h ]h"]h$]h&]uh1j"hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j#)}(hhh]jv)}(h``CONFIG_MODULE_SIG_SHA3_256``h]j)}(hj h]hCONFIG_MODULE_SIG_SHA3_256}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubah}(h]h ]h"]h$]h&]uh1juhhhKYhjubah}(h]h ]h"]h$]h&]uh1j"hjubj#)}(hhh]jv)}(h+:menuselection:`Sign modules with SHA3-256`h]j)}(hSign modules with SHA3-256h]hSign modules with SHA3-256}(hj/hhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextj-uh1jhj+ubah}(h]h ]h"]h$]h&]uh1juhhhKYhj(ubah}(h]h ]h"]h$]h&]uh1j"hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j#)}(hhh]jv)}(h``CONFIG_MODULE_SIG_SHA3_384``h]j)}(hjYh]hCONFIG_MODULE_SIG_SHA3_384}(hj[hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjWubah}(h]h ]h"]h$]h&]uh1juhhhKZhjTubah}(h]h ]h"]h$]h&]uh1j"hjQubj#)}(hhh]jv)}(h+:menuselection:`Sign modules with SHA3-384`h]j)}(hSign modules with SHA3-384h]hSign modules with SHA3-384}(hj{hhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextjyuh1jhjwubah}(h]h ]h"]h$]h&]uh1juhhhKZhjtubah}(h]h ]h"]h$]h&]uh1j"hjQubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j#)}(hhh]jv)}(h``CONFIG_MODULE_SIG_SHA3_512``h]j)}(hjh]hCONFIG_MODULE_SIG_SHA3_512}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1juhhhK[hjubah}(h]h ]h"]h$]h&]uh1j"hjubj#)}(hhh]jv)}(h+:menuselection:`Sign modules with SHA3-512`h]j)}(hSign modules with SHA3-512h]hSign modules with SHA3-512}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextjuh1jhjubah}(h]h ]h"]h$]h&]uh1juhhhK[hjubah}(h]h ]h"]h$]h&]uh1j"hjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]colsKuh1jhjubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1jhhhKUhjubjv)}(hThe algorithm selected here will also be built into the kernel (rather than being a module) so that modules signed with that algorithm can have their signatures checked without causing a dependency loop.h]hThe algorithm selected here will also be built into the kernel (rather than being a module) so that modules signed with that algorithm can have their signatures checked without causing a dependency loop.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhK^hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hX:menuselection:`File name or PKCS#11 URI of module signing key` (``CONFIG_MODULE_SIG_KEY``) Setting this option to something other than its default of ``certs/signing_key.pem`` will disable the autogeneration of signing keys and allow the kernel modules to be signed with a key of your choosing. The string provided should identify a file containing both a private key and its corresponding X.509 certificate in PEM form, or — on systems where the OpenSSL ENGINE_pkcs11 is functional — a PKCS#11 URI as defined by RFC7512. In the latter case, the PKCS#11 URI should reference both a certificate and a private key. If the PEM file containing the private key is encrypted, or if the PKCS#11 token requires a PIN, this can be provided at build time by means of the ``KBUILD_SIGN_PIN`` variable. h](jv)}(h[:menuselection:`File name or PKCS#11 URI of module signing key` (``CONFIG_MODULE_SIG_KEY``)h](j)}(h.File name or PKCS#11 URI of module signing keyh]h.File name or PKCS#11 URI of module signing key}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtext?:menuselection:`File name or PKCS#11 URI of module signing key`uh1jhjubh (}(hjhhhNhNubj)}(h``CONFIG_MODULE_SIG_KEY``h]hCONFIG_MODULE_SIG_KEY}(hj3hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh)}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhKchjubjv)}(hX Setting this option to something other than its default of ``certs/signing_key.pem`` will disable the autogeneration of signing keys and allow the kernel modules to be signed with a key of your choosing. The string provided should identify a file containing both a private key and its corresponding X.509 certificate in PEM form, or — on systems where the OpenSSL ENGINE_pkcs11 is functional — a PKCS#11 URI as defined by RFC7512. In the latter case, the PKCS#11 URI should reference both a certificate and a private key.h](h;Setting this option to something other than its default of }(hjKhhhNhNubj)}(h``certs/signing_key.pem``h]hcerts/signing_key.pem}(hjShhhNhNubah}(h]h ]h"]h$]h&]uh1jhjKubhX will disable the autogeneration of signing keys and allow the kernel modules to be signed with a key of your choosing. The string provided should identify a file containing both a private key and its corresponding X.509 certificate in PEM form, or — on systems where the OpenSSL ENGINE_pkcs11 is functional — a PKCS#11 URI as defined by RFC7512. In the latter case, the PKCS#11 URI should reference both a certificate and a private key.}(hjKhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhKfhjubjv)}(hIf the PEM file containing the private key is encrypted, or if the PKCS#11 token requires a PIN, this can be provided at build time by means of the ``KBUILD_SIGN_PIN`` variable.h](hIf the PEM file containing the private key is encrypted, or if the PKCS#11 token requires a PIN, this can be provided at build time by means of the }(hjkhhhNhNubj)}(h``KBUILD_SIGN_PIN``h]hKBUILD_SIGN_PIN}(hjshhhNhNubah}(h]h ]h"]h$]h&]uh1jhjkubh variable.}(hjkhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhKohjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(h:menuselection:`Additional X.509 keys for default system keyring` (``CONFIG_SYSTEM_TRUSTED_KEYS``) This option can be set to the filename of a PEM-encoded file containing additional certificates which will be included in the system keyring by default. h](jv)}(hb:menuselection:`Additional X.509 keys for default system keyring` (``CONFIG_SYSTEM_TRUSTED_KEYS``)h](j)}(h0Additional X.509 keys for default system keyringh]h0Additional X.509 keys for default system keyring}(hjhhhNhNubah}(h]h ] menuselectionah"]h$]h&]rawtextA:menuselection:`Additional X.509 keys for default system keyring`uh1jhjubh (}(hjhhhNhNubj)}(h``CONFIG_SYSTEM_TRUSTED_KEYS``h]hCONFIG_SYSTEM_TRUSTED_KEYS}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh)}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhKthjubjv)}(hThis option can be set to the filename of a PEM-encoded file containing additional certificates which will be included in the system keyring by default.h]hThis option can be set to the filename of a PEM-encoded file containing additional certificates which will be included in the system keyring by default.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKwhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]enumtypearabicprefix(suffix)uh1jhjubah}(h]h ]h"]h$]h&]uh1jhhhK3hjhhubjv)}(hNote that enabling module signing adds a dependency on the OpenSSL devel packages to the kernel build processes for the tool that does the signing.h]hNote that enabling module signing adds a dependency on the OpenSSL devel packages to the kernel build processes for the tool that does the signing.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhK{hjhhubeh}(h]configuring-module-signingah ]h"]configuring module signingah$]h&]uh1hhhhhhhhK)ubh)}(hhh](h)}(hGenerating signing keysh]hGenerating signing keys}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubjv)}(hXCryptographic keypairs are required to generate and check signatures. A private key is used to generate a signature and the corresponding public key is used to check it. The private key is only needed during the build, after which it can be deleted or stored securely. The public key gets built into the kernel so that it can be used to check the signatures as the modules are loaded.h]hXCryptographic keypairs are required to generate and check signatures. A private key is used to generate a signature and the corresponding public key is used to check it. The private key is only needed during the build, after which it can be deleted or stored securely. The public key gets built into the kernel so that it can be used to check the signatures as the modules are loaded.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKhjhhubjv)}(hUnder normal conditions, when ``CONFIG_MODULE_SIG_KEY`` is unchanged from its default, the kernel build will automatically generate a new keypair using openssl if one does not exist in the file::h](hUnder normal conditions, when }(hj!hhhNhNubj)}(h``CONFIG_MODULE_SIG_KEY``h]hCONFIG_MODULE_SIG_KEY}(hj)hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj!ubh is unchanged from its default, the kernel build will automatically generate a new keypair using openssl if one does not exist in the file:}(hj!hhhNhNubeh}(h]h ]h"]h$]h&]uh1juhhhKhjhhubj)}(hcerts/signing_key.pemh]hcerts/signing_key.pem}hjAsbah}(h]h ]h"]h$]h&]hhuh1jhhhKhjhhubjv)}(htduring the building of vmlinux (the public part of the key needs to be built into vmlinux) using parameters in the::h]hsduring the building of vmlinux (the public part of the key needs to be built into vmlinux) using parameters in the:}(hjOhhhNhNubah}(h]h ]h"]h$]h&]uh1juhhhKhjhhubj)}(hcerts/x509.genkeyh]hcerts/x509.genkey}hj]sbah}(h]h ]h"]h$]h&]hhuh1jhhhKhjhhubjv)}(h jjjjjDjAj%j"jjj< j9 j j j j j9 j6 u nametypes}(jA jjjDj%jj< j j j9 uh}(j> hjjdjjjAjj"jGjj(j9 jj j? j j j6 j u footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages]transform_messages] transformerN include_log] decorationNhhub.