Searched refs:verified (Results 1 – 25 of 75) sorted by relevance
123
| /linux-5.19.10/crypto/asymmetric_keys/ |
| D | pkcs7_trust.c | 40 if (x509->verified) in pkcs7_validate_trust_one()
41 goto verified; in pkcs7_validate_trust_one()
124 verified: in pkcs7_validate_trust_one()
126 x509->verified = true; in pkcs7_validate_trust_one()
128 p->verified = true; in pkcs7_validate_trust_one()
|
| D | x509_parser.h | 37 bool verified; member
|
| /linux-5.19.10/Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 127 Hash blocks are still verified each time they are read from the hash device,
129 blocks, and a hash block will not be verified any more after all the data
130 blocks it covers have been verified anyway.
147 dm-verity is meant to be set up as part of a verified boot path. This
153 After instantiation, all hashes will be verified on-demand during
154 disk access. If they cannot be verified up to the root node of the
164 corrupted data will be verified using the cryptographic hash of the
206 the command-line is verified.
|
| /linux-5.19.10/Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 41 - Chrome OS verified boot data
285 - Offset in CMOS bank 0 of the verified boot non-volatile storage block, counting from
291 - Size in bytes of the verified boot non-volatile storage block.
307 VDTA (Chrome OS verified boot data)
309 This control method returns the verified boot data block shared between the firmware
318 A buffer containing the verified boot data block.
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-driver-chromeos-acpi | 119 Returns offset in CMOS bank 0 of the verified boot non-volatile
128 Return the size in bytes of the verified boot non-volatile
135 Returns the verified boot data block shared between the
|
| D | sysfs-class-chromeos-driver-cros-ec-vbc | 5 Read/write the verified boot context data included on a
|
| D | sysfs-firmware-ofw | 48 blob, and verified at late_initcall time. The sysfs
|
| D | sysfs-driver-w1_therm | 63 actual resolution is read back from the chip and verified. Error
|
| /linux-5.19.10/tools/memory-model/scripts/ |
| D | checkalllitmus.sh | 64 echo All litmus tests verified as was expected. 1>&2
|
| /linux-5.19.10/Documentation/admin-guide/sysctl/ |
| D | user.rst | 26 verified to be below the per user limit in that user namespace.
30 in (user namespaces can be nested) and verified to be below the per user
|
| /linux-5.19.10/security/integrity/ima/ |
| D | Kconfig | 203 be signed and verified by a public key on the trusted IMA
206 Kernel image signatures can not be verified by the original
216 and verified by a public key on the trusted IMA keyring.
218 Kernel module signatures can only be verified by IMA-appraisal,
228 and verified by a key on the trusted IMA keyring.
|
| /linux-5.19.10/arch/arm64/boot/dts/qcom/ |
| D | msm8992-lg-bullhead.dtsi | 263 /* TODO: get this verified
276 /* TODO: get this verified
|
| /linux-5.19.10/Documentation/devicetree/bindings/arm/ |
| D | arm,corstone1000.yaml | 14 ARM's Corstone1000 includes pre-verified Corstone SSE-710 subsystem that
|
| /linux-5.19.10/Documentation/w1/slaves/ |
| D | w1_ds2413.rst | 33 Bit 4-7: Complement of Bit 3 to Bit 0 (verified by the kernel module)
|
| /linux-5.19.10/Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 8 such as dm-verity or CDROM. This allows systems that have a verified
|
| /linux-5.19.10/Documentation/networking/ |
| D | driver.rst | 86 be verified. For example, for ethernet check it with
|
| /linux-5.19.10/Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 45 Generic timing routine has been verified to work properly on
|
| /linux-5.19.10/fs/ext4/ |
| D | balloc.c | 385 goto verified; in ext4_validate_block_bitmap()
405 verified: in ext4_validate_block_bitmap()
|
| /linux-5.19.10/Documentation/devicetree/bindings/mfd/ |
| D | google,cros-ec.yaml | 53 store verified boot context data. This boolean flag is used to specify
|
| /linux-5.19.10/Documentation/s390/ |
| D | driver-model.rst | 171 verified that the device is not already online.
185 verified that the device is online.
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | fsverity.rst | 26 automatically verified against the file's Merkle tree. Reads of any
506 fs-verity. In this case, the plaintext data is verified rather than
553 fs-verity ensures that all reads of a verity file's data are verified,
557 already verified). Below, we describe how filesystems implement this.
587 an already-verified hash page is seen, as indicated by the PageChecked
607 encrypted, the pages must be decrypted before being verified. To
790 Uptodate until they've been verified. Currently, each
|
| D | xfs-self-describing-metadata.rst | 96 metadata block can be verified as being in the correct place without needing to
182 is extensively verified and if it is OK we then update the LSN from the last
345 inode is already extensively verified during writeback in xfs_iflush_int, so the
|
| /linux-5.19.10/Documentation/bpf/ |
| D | prog_cgroup_sysctl.rst | 80 string value set by the helper is treated and verified by kernel same way as
|
| /linux-5.19.10/certs/ |
| D | Kconfig | 51 userspace may only add extra keys if those keys can be verified by
|
| /linux-5.19.10/Documentation/i2c/ |
| D | fault-codes.rst | 104 have verified that functionality was supported before it
|
123