Lines Matching refs:signature

23 installation and then checks the signature upon loading the module.  This
27 signature checking is done by the kernel so that it is not necessary to have
35 SHA-512 (the algorithm is selected by data in the signature).
45 	CONFIG_MODULE_SIG	"Module signature verification"
52      signature for which the key is not known or a module that is unsigned.
60      signature that can be verified by a public key in the kernel's possession
63      Irrespective of the setting here, if the module has a signature block that
123 private key is used to generate a signature and the corresponding public key is
234 A signed module has a digital signature simply appended at the end.  The string
235 "~Module signature appended~." at the end of the module's file confirms that a
236 signature is present but it does not confirm that the signature is valid!
238 Signed modules are BRITTLE as the signature is outside of the defined ELF
239 container.  Thus they MAY NOT be stripped once the signature is computed and
250 signature checking is all done within the kernel.
261 a signature mismatch will not be permitted to load.
263 Any module that has an unparseable signature will be rejected.