| /Linux-v5.4/drivers/scsi/ |
| D | fdomain_isa.c | 65 } signatures[] = { variable
84 #define SIGNATURE_COUNT ARRAY_SIZE(signatures)
101 if (check_signature(p + signatures[i].offset, in fdomain_isa_match()
102 signatures[i].signature, in fdomain_isa_match()
103 signatures[i].length)) in fdomain_isa_match()
107 sig = &signatures[i]; in fdomain_isa_match()
|
| D | aha152x.c | 2949 } signatures[] = variable
3251 for (j = 0; j<ARRAY_SIZE(signatures) && !ok; j++) in aha152x_init()
3252 ok = check_signature(p + signatures[j].sig_offset, in aha152x_init()
3253 signatures[j].signature, signatures[j].sig_length); in aha152x_init()
|
| /Linux-v5.4/security/integrity/ima/ |
| D | Kconfig | 186 bool "Appraise firmware signatures"
196 bool "Appraise kexec kernel image signatures"
204 Kernel image signatures can not be verified by the original
209 bool "Appraise kernel modules signatures"
216 Kernel module signatures can only be verified by IMA-appraisal,
237 bool "Support module-style signatures for appraisal"
244 Adds support for signatures appended to files. The format of the
247 to accept such signatures.
|
| /Linux-v5.4/Documentation/ |
| D | digsig.txt | 20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
82 to generate signatures, to load keys into the kernel keyring.
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | module-signing.rst | 13 .. - Non-valid signatures and unsigned modules.
30 involved. The signatures are not themselves encoded in any industrial standard
93 their signatures checked without causing a dependency loop.
128 Cryptographic keypairs are required to generate and check signatures. A
132 kernel so that it can be used to check the signatures as the modules are
260 Non-valid signatures and unsigned modules
|
| /Linux-v5.4/scripts/ |
| D | get_maintainer.pl | 1580 my @signatures = ();
1595 @signatures = grep(/^[ \t]*${signature_pattern}.*\@.*$/, @lines);
1600 return (0, \@signatures, \@authors, \@stats) if !@signatures;
1606 @signatures = grep(!/${penguin_chiefs}/i, @signatures);
1610 my ($types_ref, $signers_ref) = extract_formatted_signatures(@signatures);
2096 my @signatures = ($line);
2097 my ($types_ref, $signers_ref) = extract_formatted_signatures(@signatures);
|
| D | checkpatch.pl | 2329 my %signatures = ();
2686 if (defined $signatures{$sig_nospace}) {
2690 $signatures{$sig_nospace} = 1;
|
| /Linux-v5.4/drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ |
| D | acr_r364.c | 35 u32 signatures[4]; member
|
| D | acr_r367.c | 324 u32 signatures[4]; member
|
| D | acr_r352.c | 115 u32 signatures[4]; member
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | reproducible-builds.rst | 93 3. Create detached signatures for the modules, and publish them as
96 4. Perform a second build that attaches the module signatures. It
|
| /Linux-v5.4/Documentation/x86/ |
| D | zero-page.rst | 41 290/040 ALL edd_mbr_sig_buffer EDD MBR signatures
|
| D | pti.rst | 164 Bugs in PTI cause a few different signatures of crashes
|
| /Linux-v5.4/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 29 Both git repositories and tarballs carry PGP signatures of the kernel
30 developers who create official kernel releases. These signatures offer a
35 - git repositories provide PGP signatures on all tags
36 - tarballs provide detached PGP signatures with all downloads
153 key using certifying key signatures (certificates). It is important to
234 much faster computationally and creates much smaller signatures when
250 The more signatures you have on your PGP key from other developers, the
410 your signatures (if they know the passphrase). Furthermore, each time a
769 verification, so it properly processes signatures made by ECC keys.
787 signatures. Furthermore, when rebasing your repository to match
[all …]
|
| D | email-clients.rst | 51 Don't use PGP/GPG signatures in mail that contains patches.
|
| /Linux-v5.4/fs/verity/ |
| D | Kconfig | 45 Support verifying signatures of verity files against the X.509
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | evm | 67 to be added at runtime. Any signatures generated after
|
| D | ima_policy | 109 Example of appraise rule allowing modsig appended signatures:
|
| /Linux-v5.4/Documentation/crypto/ |
| D | asymmetric-keys.txt | 239 have various checks that can be performed on it (eg. self-signatures, validity
402 A single keyring can be used to verify a chain of signatures by
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 143 has been authenticated in some way (cryptographic signatures, etc).
|
| /Linux-v5.4/Documentation/bpf/ |
| D | btf.rst | 495 pretty print types, dump func signatures and line info, etc.
617 func signatures and line info, along with byte/jit codes.
|
| /Linux-v5.4/Documentation/input/devices/ |
| D | alps.rst | 17 choice was made. The new touchpad signatures are named: "Rushmore",
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | ubifs-authentication.rst | 426 UBIFS can exchange all digital signatures with HMACs on first mount similar
|
| /Linux-v5.4/Documentation/security/keys/ |
| D | core.rst | 914 chains or individual certificate signatures using the asymmetric key type.
|
| /Linux-v5.4/init/ |
| D | Kconfig | 2056 Check modules for valid signatures upon load: the signature
|
