Lines Matching refs:be

33 standard (though it is pluggable and permits others to be used).  The possible
34 hash algorithms that can be used are SHA-1, SHA-224, SHA-256, SHA-384, and
49  (1) "Require modules to be validly signed" (CONFIG_MODULE_SIG_FORCE)
56      be marked as being tainted, and the concerned modules will be marked as
60      signature that can be verified by a public key in the kernel's possession
61      will be loaded.  All other modules will generate an error.
64      cannot be parsed, it will be rejected out of hand.
69      If this is on then modules will be automatically signed during the
71      be signed manually using:
76  (3) "Which hash algorithm should modules be signed with?"
87      The algorithm selected here will also be built into the kernel (rather
99 it can be deleted or stored securely.  The public key gets built into the
100 kernel so that it can be used to check the signatures as the modules are
109 during the building of vmlinux (the public part of the key needs to be built
119 should be altered from the default:
126 The generated RSA key size can also be set with:
146 The kernel contains a ring of public keys that can be viewed by root.  They're
147 in a keyring called ".system_keyring" that can be seen by:
157 whose name is suffixed with ".x509" will be assumed to be an X.509 public key
158 and will be added to the keyring.
171 Note, however, that the kernel will only permit keys to be added to
186 	4.  The kernel module to be signed
195 kernel or can be loaded without requiring itself.
207 container.  Thus they MAY NOT be stripped once the signature is computed and
229 a signature mismatch will not be permitted to load.
231 Any module that has an unparseable signature will be rejected.
240 private key must be either destroyed or moved to a secure location and not kept