| /linux/tools/testing/selftests/arm64/pauth/ |
| A D | pac.c | 39 void sign_specific(struct signatures *sign, size_t val) in sign_specific()
47 void sign_all(struct signatures *sign, size_t val) in sign_all()
56 int n_same(struct signatures *old, struct signatures *new, int nkeys) in n_same()
70 int n_same_single_set(struct signatures *sign, int nkeys) in n_same_single_set()
257 struct signatures signed_vals; in TEST()
296 struct signatures new_keys; in TEST()
297 struct signatures old_keys; in TEST()
330 struct signatures trash; in TEST()
331 struct signatures before; in TEST()
332 struct signatures after; in TEST()
[all …]
|
| A D | exec_target.c | 12 struct signatures signed_vals; in main()
31 fwrite(&signed_vals, sizeof(struct signatures), 1, stdout); in main()
|
| A D | helper.h | 11 struct signatures { struct
|
| /linux/drivers/scsi/ |
| A 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()
|
| A D | aha152x.c | 2995 } signatures[] = variable
3297 for (j = 0; j<ARRAY_SIZE(signatures) && !ok; j++) in aha152x_init()
3298 ok = check_signature(p + signatures[j].sig_offset, in aha152x_init()
3299 signatures[j].signature, signatures[j].sig_length); in aha152x_init()
|
| /linux/security/integrity/ima/ |
| A D | Kconfig | 183 bool "Appraise firmware signatures"
193 bool "Appraise kexec kernel image signatures"
201 Kernel image signatures can not be verified by the original
206 bool "Appraise kernel modules signatures"
213 Kernel module signatures can only be verified by IMA-appraisal,
234 bool "Support module-style signatures for appraisal"
241 Adds support for signatures appended to files. The format of the
244 to accept such signatures.
|
| /linux/fs/verity/ |
| A D | Kconfig | 43 fs-verity builtin signatures.
46 the only way to do signatures with fs-verity, and the
|
| /linux/Documentation/security/ |
| A D | digsig.rst | 20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
82 to generate signatures, to load keys into the kernel keyring.
|
| A D | ipe.rst | 70 * No need for two signatures (IMA, then EVM): one signature covers
180 trusted to be changed. This is done through signatures, resulting in needing
|
| /linux/drivers/gpu/drm/nouveau/include/nvfw/ |
| A D | acr.h | 180 u32 signatures[4]; member
210 u32 signatures[4]; member
|
| /linux/Documentation/admin-guide/ |
| A D | module-signing.rst | 13 .. - Non-valid signatures and unsigned modules.
30 involved. The signatures are not themselves encoded in any industrial standard
94 their signatures checked without causing a dependency loop.
129 Cryptographic keypairs are required to generate and check signatures. A
133 kernel so that it can be used to check the signatures as the modules are
265 Non-valid signatures and unsigned modules
|
| /linux/Documentation/ABI/testing/ |
| A D | ima_policy | 56 limited to fsverity digest based signatures
146 Example of appraise rule allowing modsig appended signatures:
172 signatures (format version 3) stored in security.ima xattr.
|
| A D | evm | 57 signatures have been solved.
103 to be added at runtime. Any signatures generated after
|
| A D | sysfs-class-firmware-attributes | 438 signatures when setting the signing key. When written,
449 public key that will be used by the BIOS to verify signatures
|
| /linux/Documentation/devicetree/bindings/nvmem/ |
| A D | nintendo-otp.yaml | 11 which contains common and per-console keys, signatures and related data
|
| /linux/scripts/ |
| A D | get_maintainer.pl | 1607 my @signatures = ();
1622 @signatures = grep(/^[ \t]*${signature_pattern}.*\@.*$/, @lines);
1627 return (0, \@signatures, \@authors, \@stats) if !@signatures;
1633 @signatures = grep(!/${penguin_chiefs}/i, @signatures);
1637 my ($types_ref, $signers_ref) = extract_formatted_signatures(@signatures);
2149 my @signatures = ($line);
2150 my ($types_ref, $signers_ref) = extract_formatted_signatures(@signatures);
|
| /linux/Documentation/process/ |
| A 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
212 The more signatures you have on your PGP key from other developers, the
370 your signatures (if they know the passphrase). Furthermore, each time a
734 signatures. Furthermore, when rebasing your repository to match
749 signatures will be valuable for such purposes.
786 purpose that puts cryptographic attestation signatures into message
809 Checking patatt signatures
[all …]
|
| A D | email-clients.rst | 56 Don't use PGP/GPG signatures in mail that contains patches.
|
| /linux/Documentation/kbuild/ |
| A 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/Documentation/arch/x86/ |
| A D | zero-page.rst | 43 290/040 ALL edd_mbr_sig_buffer EDD MBR signatures
|
| A D | pti.rst | 162 Bugs in PTI cause a few different signatures of crashes
|
| /linux/Documentation/filesystems/ |
| A D | fsverity.rst | 81 library that supports digital signatures.
91 including those protected by fs-verity's built-in signatures.
451 verification of fs-verity builtin signatures.
454 It is not the only way to do signatures with fs-verity, and the
491 signatures are not the only way to do signatures with fs-verity. See
493 fs-verity builtin signatures have some major limitations that should
534 - fs-verity builtin signatures are in PKCS#7 format, and the public
537 builtin signatures use them), and are very feature rich.
545 Ed25519 keys and signatures, and verifying signatures in userspace.
548 still consider that verifying those signatures in userspace is more
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A D | verity.rst | 137 being set in the kernel. The signatures are checked against the builtin
156 has been authenticated in some way (cryptographic signatures, etc).
|
| /linux/Documentation/crypto/ |
| A D | asymmetric-keys.rst | 235 have various checks that can be performed on it (eg. self-signatures, validity
397 A single keyring can be used to verify a chain of signatures by
|
| /linux/drivers/md/ |
| A D | Kconfig | 539 Rely on the secondary trusted keyring to verify dm-verity signatures.
549 Rely also on the platform keyring to verify dm-verity signatures.
|