Lines Matching full:key

14 .. - Administering/protecting the private key.
24 or modules signed with an invalid key.  Module signing increases security by
32 public key signing standard (though it is pluggable and permits others to be
53      signature for which the key is not known or a module that is unsigned.
55      If this is off (ie. "permissive"), then modules for which the key is not
61      signature that can be verified by a public key in the kernel's possession
97  (4) :menuselection:`File name or PKCS#11 URI of module signing key`
102      and allow the kernel modules to be signed with a key of your choosing.
103      The string provided should identify a file containing both a private key
107      certificate and a private key.
109      If the PEM file containing the private key is encrypted, or if the
130 private key is used to generate a signature and the corresponding public key is
131 used to check it.  The private key is only needed during the build, after which
132 it can be deleted or stored securely.  The public key gets built into the
142 during the building of vmlinux (the public part of the key needs to be built
160 	CN = Build time autogenerated kernel key
163 The generated RSA key size can also be set with::
169 It is also possible to manually generate the key private/public files using the
170 x509.genkey key generation configuration file in the root node of the Linux
172 generate the public/private key files::
179 in the ``CONFIG_MODULE_SIG_KEY`` option, and the certificate and key therein will
193 …302d2d52 I------     1 perm 1f010000     0     0 asymmetri Fedora kernel signing key: d69a84e6bce3…
196 Beyond the public key generated specifically for module signing, additional
201 add those in also (e.g. from the UEFI key database).
205 	keyctl padd asymmetric "" [.builtin_trusted_keys-ID] <[key-file]
212 ``.builtin_trusted_keys`` **if** the new key's X.509 wrapper is validly signed by a key
213 that is already resident in the ``.builtin_trusted_keys`` at the time the key was added.
224 	2.  The private key filename or PKCS#11 URI
225 	3.  The public key filename
237 If the private key requires a passphrase or PIN, it can be provided in the
270 for which it has a public key.   Otherwise, it will also load modules that are
271 unsigned.   Any module for which the kernel has a key, but which proves to have
278 Administering/protecting the private key
281 Since the private key is used to sign modules, viruses and malware could use
282 the private key to sign modules and compromise the operating system.  The
283 private key must be either destroyed or moved to a secure location and not kept
286 If you use the same private key to sign modules for multiple kernel