Lines Matching refs: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 SHA-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
129 private key is used to generate a signature and the corresponding public key is
240 A signed module has a digital signature simply appended at the end.  The string
241 ``~Module signature appended~.`` at the end of the module's file confirms that a
242 signature is present but it does not confirm that the signature is valid!
244 Signed modules are BRITTLE as the signature is outside of the defined ELF
245 container.  Thus they MAY NOT be stripped once the signature is computed and
256 done in userspace.  The signature checking is all done within the kernel.
267 a signature mismatch will not be permitted to load.
269 Any module that has an unparseable signature will be rejected.