| /linux/crypto/asymmetric_keys/ |
| A 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()
|
| A D | x509_parser.h | 37 bool verified; member
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A 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/Documentation/admin-guide/sysctl/ |
| A 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/Documentation/ABI/testing/ |
| A D | sysfs-class-chromeos-driver-cros-ec-vbc | 5 Read/write the verified boot context data included on a
|
| A D | sysfs-firmware-ofw | 48 blob, and verified at late_initcall time. The sysfs
|
| A D | sysfs-driver-w1_therm | 63 actual resolution is read back from the chip and verified. Error
|
| /linux/tools/memory-model/scripts/ |
| A D | checkalllitmus.sh | 64 echo All litmus tests verified as was expected. 1>&2
|
| /linux/security/integrity/ima/ |
| A D | Kconfig | 205 be signed and verified by a public key on the trusted IMA
208 Kernel image signatures can not be verified by the original
218 and verified by a public key on the trusted IMA keyring.
220 Kernel module signatures can only be verified by IMA-appraisal,
230 and verified by a key on the trusted IMA keyring.
|
| /linux/arch/arm64/boot/dts/qcom/ |
| A D | msm8992-bullhead-rev-101.dts | 265 /* TODO: get this verified
278 /* TODO: get this verified
|
| /linux/Documentation/w1/slaves/ |
| A D | w1_ds2413.rst | 33 Bit 4-7: Complement of Bit 3 to Bit 0 (verified by the kernel module)
|
| A D | w1_therm.rst | 81 resolution is read back from the chip and verified.
|
| /linux/Documentation/admin-guide/LSM/ |
| A D | LoadPin.rst | 8 such as dm-verity or CDROM. This allows systems that have a verified
|
| /linux/Documentation/networking/ |
| A D | driver.rst | 86 be verified. For example, for ethernet check it with
|
| /linux/fs/ext4/ |
| A D | balloc.c | 385 goto verified; in ext4_validate_block_bitmap()
405 verified: in ext4_validate_block_bitmap()
|
| /linux/Documentation/driver-api/memory-devices/ |
| A D | ti-gpmc.rst | 45 Generic timing routine has been verified to work properly on
|
| /linux/Documentation/filesystems/ |
| A D | fsverity.rst | 26 automatically verified against the file's Merkle tree. Reads of any
495 fs-verity. In this case, the plaintext data is verified rather than
542 fs-verity ensures that all reads of a verity file's data are verified,
546 already verified). Below, we describe how filesystems implement this.
576 an already-verified hash page is seen, as indicated by the PageChecked
596 encrypted, the pages must be decrypted before being verified. To
779 Uptodate until they've been verified. Currently, each
|
| A 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/Documentation/s390/ |
| A D | driver-model.rst | 171 verified that the device is not already online.
185 verified that the device is online.
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| A D | google,cros-ec.yaml | 58 store verified boot context data. This boolean flag is used to specify
|
| /linux/certs/ |
| A D | Kconfig | 52 userspace may only add extra keys if those keys can be verified by
|
| /linux/Documentation/security/keys/ |
| A D | trusted-encrypted.rst | 11 convenience, and are integrity verified.
47 environment verified via Secure/Trusted boot process.
|
| /linux/Documentation/bpf/ |
| A D | prog_cgroup_sysctl.rst | 80 string value set by the helper is treated and verified by kernel same way as
|
| /linux/Documentation/i2c/ |
| A D | fault-codes.rst | 104 have verified that functionality was supported before it
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| A D | rk3399-gru-chromebook.dtsi | 489 /* May run faster once verified. */
|