| /linux/tools/testing/selftests/arm64/pauth/ |
| H 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()
92 int exec_sign_all(struct signatures *signed_vals, size_t val) in exec_sign_all()
179 ret = read(new_stdout[0], signed_vals, sizeof(struct signatures)); in exec_sign_all()
260 struct signatures signed_vals; in TEST()
299 struct signatures new_keys; in TEST()
300 struct signatures old_keys; in TEST()
333 struct signatures trash; in TEST()
[all …]
|
| H A D | exec_target.c | 12 struct signatures signed_vals; in main()
36 fwrite(&signed_vals, sizeof(struct signatures), 1, stdout); in main()
|
| H A D | helper.h | 11 struct signatures { struct
|
| /linux/drivers/scsi/ |
| H 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()
|
| /linux/security/integrity/ima/ |
| H 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/ |
| H A D | Kconfig | 37 fs-verity builtin signatures.
40 the only way to do signatures with fs-verity, and the
|
| /linux/drivers/gpu/drm/nouveau/include/nvfw/ |
| H A D | acr.h | 180 u32 signatures[4]; member
210 u32 signatures[4]; member
|
| /linux/Documentation/security/ |
| H 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.
|
| H 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/Documentation/admin-guide/ |
| H 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/ |
| H A D | ima_policy | 57 limited to fsverity digest based signatures
147 Example of appraise rule allowing modsig appended signatures:
173 signatures (format version 3) stored in security.ima xattr.
|
| H A D | evm | 57 signatures have been solved.
103 to be added at runtime. Any signatures generated after
|
| /linux/Documentation/arch/x86/ |
| H A D | zero-page.rst | 43 290/040 ALL edd_mbr_sig_buffer EDD MBR signatures
|
| H A D | pti.rst | 162 Bugs in PTI cause a few different signatures of crashes
|
| /linux/Documentation/filesystems/ |
| H A D | fsverity.rst | 81 library that supports digital signatures.
91 including those protected by fs-verity's built-in signatures.
456 verification of fs-verity builtin signatures.
459 It is not the only way to do signatures with fs-verity, and the
496 signatures are not the only way to do signatures with fs-verity. See
498 fs-verity builtin signatures have some major limitations that should
539 - fs-verity builtin signatures are in PKCS#7 format, and the public
542 builtin signatures use them), and are very feature rich.
550 Ed25519 keys and signatures, and verifying signatures in userspace.
553 still consider that verifying those signatures in userspace is more
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | verity.rst | 146 being set in the kernel. The signatures are checked against the builtin
172 has been authenticated in some way (cryptographic signatures, etc).
|
| /linux/drivers/gpu/nova-core/gsp/ |
| H A D | fw.rs | 164 sysmemAddrOfSignature: gsp_firmware.signatures.dma_handle(), in new()
165 sizeOfSignature: u64::from_safe_cast(gsp_firmware.signatures.size()), in new()
|
| /linux/Documentation/crypto/ |
| H 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/ |
| H A D | Kconfig | 584 Rely on the secondary trusted keyring to verify dm-verity signatures.
594 Rely also on the platform keyring to verify dm-verity signatures.
|
| /linux/Documentation/input/devices/ |
| H A D | alps.rst | 17 choice was made. The new touchpad signatures are named: "Rushmore",
|
| /linux/drivers/nvmem/ |
| H A D | Kconfig | 248 This memory contains common and per-console keys, signatures and
|
| /linux/kernel/module/ |
| H A D | Kconfig | 255 Check modules for valid signatures upon load: the signature
|
| /linux/scripts/ |
| H A D | checkpatch.pl | 2713 my %signatures = ();
3183 if (defined $signatures{$sig_nospace}) {
3187 $signatures{$sig_nospace} = 1;
|
| /linux/Documentation/networking/ |
| H A D | tcp_ao.rst | 145 segments with unknown key signatures are discarded with warnings logged.
|
| /linux/Documentation/security/keys/ |
| H A D | core.rst | 914 chains or individual certificate signatures using the asymmetric key type.
|