Lines Matching full:signature

22 installation and then checks the signature upon loading the module.  This
26 signature checking is done by the kernel so that it is not necessary to have
34 sizes 256, 384, and 512 (the algorithm is selected by data in the signature).
45 	CONFIG_MODULE_SIG	"Module signature verification"
53      signature for which the key is not known or a module that is unsigned.
61      signature that can be verified by a public key in the kernel's possession
64      Irrespective of the setting here, if the module has a signature block that
130 private key is used to generate a signature and the corresponding public key is
245 A signed module has a digital signature simply appended at the end.  The string
246 ``~Module signature appended~.`` at the end of the module's file confirms that a
247 signature is present but it does not confirm that the signature is valid!
249 Signed modules are BRITTLE as the signature is outside of the defined ELF
250 container.  Thus they MAY NOT be stripped once the signature is computed and
261 done in userspace.  The signature checking is all done within the kernel.
272 a signature mismatch will not be permitted to load.
274 Any module that has an unparsable signature will be rejected.