Lines Matching refs:key

15  - Administering/protecting the private key.
25 or modules signed with an invalid key.  Module signing increases security by
32 type.  The facility currently only supports the RSA public key encryption
52      signature for which the key is not known or a module that is unsigned.
54      If this is off (ie. "permissive"), then modules for which the key is not
60      signature that can be verified by a public key in the kernel's possession
92  (4) "File name or PKCS#11 URI of module signing key" (CONFIG_MODULE_SIG_KEY)
96      and allow the kernel modules to be signed with a key of your choosing.
97      The string provided should identify a file containing both a private key
101      certificate and a private key.
103      If the PEM file containing the private key is encrypted, or if the
123 private key is used to generate a signature and the corresponding public key is
124 used to check it.  The private key is only needed during the build, after which
125 it can be deleted or stored securely.  The public key gets built into the
135 during the building of vmlinux (the public part of the key needs to be built
149 	CN = Build time autogenerated kernel key
152 The generated RSA key size can also be set with:
158 It is also possible to manually generate the key private/public files using the
159 x509.genkey key generation configuration file in the root node of the Linux
161 generate the public/private key files:
168 in the CONFIG_MODULE_SIG_KEY option, and the certificate and key therein will
182 …302d2d52 I------     1 perm 1f010000     0     0 asymmetri Fedora kernel signing key: d69a84e6bce3…
185 Beyond the public key generated specifically for module signing, additional
190 add those in also (e.g. from the UEFI key database).
194 	keyctl padd asymmetric "" [.system_keyring-ID] <[key-file]
201 .system_keyring _if_ the new key's X.509 wrapper is validly signed by a key
202 that is already resident in the .system_keyring at the time the key was added.
213 	2.  The private key filename or PKCS#11 URI
214 	3.  The public key filename
226 If the private key requires a passphrase or PIN, it can be provided in the
259 for which it has a public key.   Otherwise, it will also load modules that are
260 unsigned.   Any module for which the kernel has a key, but which proves to have
270 Since the private key is used to sign modules, viruses and malware could use
271 the private key to sign modules and compromise the operating system.  The
272 private key must be either destroyed or moved to a secure location and not kept