Home
last modified time | relevance | path

Searched refs:verity (Results 1 – 25 of 27) sorted by relevance

12

/Linux-v5.15/Documentation/filesystems/
Dfsverity.rst6 fs-verity: read-only file-based authenticity protection
12 fs-verity (``fs/verity/``) is a support layer that filesystems can
16 needed to support fs-verity.
18 fs-verity is similar to `dm-verity
19 <https://www.kernel.org/doc/Documentation/device-mapper/verity.txt>`_
21 filesystems supporting fs-verity, userspace can execute an ioctl that
30 the "fs-verity file digest", which is a hash that includes the Merkle
31 tree root hash) that fs-verity is enforcing for the file. This ioctl
34 fs-verity is essentially a way to hash a file in constant time,
41 By itself, the base fs-verity feature only provides integrity
[all …]
Dubifs-authentication.rst32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
444 [DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst
/Linux-v5.15/fs/verity/
DKconfig14 This option enables fs-verity. fs-verity is the dm-verity
17 ioctl to enable verity for a file, which causes the filesystem
29 fs-verity is especially useful on large files where not all
30 the contents may actually be needed. Also, fs-verity verifies
40 Enable debugging messages related to fs-verity by default.
42 Say N unless you are an fs-verity developer.
49 Support verifying signatures of verity files against the X.509
50 certificates that have been loaded into the ".fs-verity"
54 used to provide an authenticity guarantee for verity files, as
56 need to check that the verity bit is set in order to get an
/Linux-v5.15/Documentation/filesystems/ext4/
Dverity.rst6 ext4 supports fs-verity, which is a filesystem feature that provides
8 fs-verity is common to all filesystems that support it; see
10 fs-verity documentation. However, the on-disk layout of the verity
11 metadata is filesystem-specific. On ext4, the verity metadata is
25 - The verity descriptor, as documented in
32 - The size of the verity descriptor in bytes, as a 4-byte little
37 They can have EXT4_ENCRYPT_FL set, in which case the verity metadata
40 Verity files cannot have blocks allocated past the end of the verity
Doverview.rst27 .. include:: verity.rst
/Linux-v5.15/drivers/md/
DMakefile27 dm-verity-y += dm-verity-target.o
76 obj-$(CONFIG_DM_VERITY) += dm-verity.o
104 dm-verity-objs += dm-verity-fec.o
108 dm-verity-objs += dm-verity-verify-sig.o
DKconfig536 be called dm-verity.
546 Add ability for dm-verity device to be validated if the
559 Rely on the secondary trusted keyring to verify dm-verity signatures.
569 Add forward error correction support to dm-verity. This option
/Linux-v5.15/Documentation/admin-guide/device-mapper/
Ddm-init.rst32 <target_type> ::= "verity" | "linear" | ... (see list below)
61 `verity` allowed
85 dm-verity,,3,ro,
86 0 1638400 verity 1 /dev/sdc1 /dev/sdc2 4096 4096 204800 1 sha256
120 "verity"::
122 dm-verity,,4,ro,
123 0 1638400 verity 1 8:1 8:2 4096 4096 204800 1 sha256
Dverity.rst2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
40 dm-verity device.
105 verity <dev> is encrypted the <fec_dev> should be too.
122 rather than every time. This reduces the overhead of dm-verity so that it
147 dm-verity is meant to be set up as part of a verified boot path. This
151 When a dm-verity device is configured, it is expected that the caller
199 The verity kernel code does not read the verity metadata on-disk header.
202 verity header.
227 "0 2097152 verity 1 /dev/sda1 /dev/sda2 4096 4096 262144 1 sha256 "\
Dindex.rst37 verity
Ddm-ima.rst15 target types like crypt, verity, integrity etc. Each of these target
338 #. verity
673 10. verity
676 section above) has the following data format for 'verity' target.
685 target_name := "target_name=verity"
704 When a 'verity' target is loaded, then IMA ASCII measurement log will have an entry
705 similar to the following, depicting what 'verity' attributes are measured in EVENT_DATA
710 name=test-verity,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
711 …target_index=0,target_begin=0,target_len=1953120,target_name=verity,target_version=1.8.0,hash_fail…
/Linux-v5.15/fs/f2fs/
DMakefile10 f2fs-$(CONFIG_FS_VERITY) += verity.o
Dsysfs.c760 F2FS_FEATURE_RO_ATTR(verity);
886 ATTR_LIST(verity),
917 F2FS_SB_FEATURE_RO_ATTR(verity, VERITY);
/Linux-v5.15/fs/ext4/
DMakefile19 ext4-$(CONFIG_FS_VERITY) += verity.o
Dsysfs.c314 EXT4_ATTR_FEATURE(verity);
334 ATTR_LIST(verity),
Dinode.c1287 bool verity = ext4_verity_in_progress(inode); in ext4_write_end() local
1302 if (!verity) in ext4_write_end()
1307 if (old_size < pos && !verity) in ext4_write_end()
1318 if (pos + len > inode->i_size && !verity && ext4_can_truncate(inode)) in ext4_write_end()
1329 if (pos + len > inode->i_size && !verity) { in ext4_write_end()
1390 bool verity = ext4_verity_in_progress(inode); in ext4_journalled_write_end() local
1414 if (!verity) in ext4_journalled_write_end()
1421 if (old_size < pos && !verity) in ext4_journalled_write_end()
1430 if (pos + len > inode->i_size && !verity && ext4_can_truncate(inode)) in ext4_journalled_write_end()
1440 if (pos + len > inode->i_size && !verity) { in ext4_journalled_write_end()
Dext4.h2115 EXT4_FEATURE_RO_COMPAT_FUNCS(verity, VERITY) in EXT4_FEATURE_COMPAT_FUNCS()
/Linux-v5.15/security/loadpin/
DKconfig12 dm-verity or a CDROM.
/Linux-v5.15/Documentation/admin-guide/LSM/
DLoadPin.rst8 such as dm-verity or CDROM. This allows systems that have a verified
/Linux-v5.15/fs/btrfs/
DMakefile39 btrfs-$(CONFIG_FS_VERITY) += verity.o
Dsysfs.c291 BTRFS_FEAT_ATTR_COMPAT_RO(verity, VERITY);
319 BTRFS_FEAT_ATTR_PTR(verity),
/Linux-v5.15/fs/
DMakefile39 obj-$(CONFIG_FS_VERITY) += verity/
DKconfig121 source "fs/verity/Kconfig"
/Linux-v5.15/Documentation/ABI/testing/
Dsysfs-fs-f2fs210 verity, sb_checksum, casefold, readonly, compression, pin_file.
220 verity, sb_checksum, casefold, readonly, compression.
230 inode_crtime, lost_found, verity, sb_checksum,
/Linux-v5.15/Documentation/admin-guide/
Dext4.rst96 * file-based verity support (fsverity)

12