Home
last modified time | relevance | path

Searched refs:verified (Results 1 – 25 of 58) sorted by relevance

123

/linux/crypto/asymmetric_keys/
H A Dpkcs7_trust.c40 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()
/linux/Documentation/firmware-guide/acpi/
H A Dchromeos-acpi-device.rst40 - Chrome OS verified boot data
284 - Offset in CMOS bank 0 of the verified boot non-volatile storage block, counting from
290 - Size in bytes of the verified boot non-volatile storage block.
306 VDTA (Chrome OS verified boot data)
308 This control method returns the verified boot data block shared between the firmware
317 A buffer containing the verified boot data block.
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-chromeos-acpi132 Returns offset in CMOS bank 0 of the verified boot non-volatile
142 Return the size in bytes of the verified boot non-volatile
150 Returns the verified boot data block shared between the
H A Dsysfs-class-chromeos-driver-cros-ec-vbc5 Read/write the verified boot context data included on a
H A Dsysfs-firmware-ofw48 blob, and verified at late_initcall time. The sysfs
H A Dsysfs-driver-w1_therm63 actual resolution is read back from the chip and verified. Error
/linux/tools/memory-model/scripts/
H A Dchecktheselitmus.sh41 echo All litmus tests verified as was expected. 1>&2
H A Dcheckalllitmus.sh63 echo All litmus tests verified as was expected. 1>&2
/linux/Documentation/admin-guide/sysctl/
H A Duser.rst26 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/security/integrity/ima/
H A DKconfig198 be signed and verified by a public key on the trusted IMA
201 Kernel image signatures can not be verified by the original
211 and verified by a public key on the trusted IMA keyring.
213 Kernel module signatures can only be verified by IMA-appraisal,
223 and verified by a key on the trusted IMA keyring.
/linux/Documentation/gpu/nova/core/
H A Dfalcon.rst34 the chip. The HS binary includes a signature in it which is verified at boot.
62 memory into the Falcon's IMEM/DMEM. Once the HS ucode is loaded, it is verified
65 Once the verified HS code is running on a Falcon, it can verify and load other
80 verified by the hardware and run, the CPU itself typically does not load
/linux/Documentation/w1/slaves/
H A Dw1_ds2413.rst33 Bit 4-7: Complement of Bit 3 to Bit 0 (verified by the kernel module)
/linux/Documentation/admin-guide/LSM/
H A DLoadPin.rst8 such as dm-verity or CDROM. This allows systems that have a verified
/linux/Documentation/networking/
H A Ddriver.rst14 be verified. For example, for ethernet check it with
/linux/Documentation/security/tpm/
H A Dtpm-security.rst117 then be verified by certification in user-space. Therefore, this chain
170 certificate itself must be verified to chain back to the manufacturer
206 signature of the returned certifyInfo is verified against the public
/linux/Documentation/driver-api/memory-devices/
H A Dti-gpmc.rst45 Generic timing routine has been verified to work properly on
/linux/Documentation/filesystems/xfs/
H A Dxfs-self-describing-metadata.rst97 metadata block can be verified as being in the correct place without needing to
183 is extensively verified and if it is OK we then update the LSN from the last
346 inode is already extensively verified during writeback in xfs_iflush_int, so the
/linux/Documentation/bpf/
H A Dprog_cgroup_sysctl.rst80 string value set by the helper is treated and verified by kernel same way as
/linux/Documentation/i2c/
H A Dfault-codes.rst108 have verified that functionality was supported before it
/linux/Documentation/admin-guide/mm/
H A Dmultigen_lru.rst48 verified on x86 varieties other than Intel and AMD. If it is
/linux/Documentation/userspace-api/
H A Dcheck_exec.rst130 user session) where scripts' integrity is verified (e.g. with IMA/EVM or
/linux/Documentation/filesystems/nfs/
H A Dnfsd-io-modes.rst121 verified to have proper offset/len (logical_block_size) and
/linux/Documentation/crypto/
H A Dasymmetric-keys.rst420 be linked will be verified using the signing key. The requested key is added
421 to the keyring only if the signature is successfully verified. -ENOKEY is
/linux/Documentation/driver-api/
H A Ddevice_link.rst236 verified upon device link addition that the supplier is not dependent
280 verified by checking the consumer device is not in the wait_for_suppliers
/linux/Documentation/driver-api/usb/
H A Ddwc3.rst59 gadget drivers. We have verified both *ConfigFS* [#configfs]_ and
124 After all these are verified, then here's how to capture enough

123