Home
last modified time | relevance | path

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

/Linux-v5.4/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
31 that fs-verity is enforcing for the file. This ioctl executes in
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
44 However, because fs-verity makes retrieving the file hash extremely
[all …]
Dubifs-authentication.rst28 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
440 [DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst
/Linux-v5.4/fs/verity/
DKconfig10 This option enables fs-verity. fs-verity is the dm-verity
13 ioctl to enable verity for a file, which causes the filesystem
25 fs-verity is especially useful on large files where not all
26 the contents may actually be needed. Also, fs-verity verifies
36 Enable debugging messages related to fs-verity by default.
38 Say N unless you are an fs-verity developer.
45 Support verifying signatures of verity files against the X.509
46 certificates that have been loaded into the ".fs-verity"
50 used to provide an authenticity guarantee for verity files, as
52 need to check that the verity bit is set in order to get an
/Linux-v5.4/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.4/drivers/md/
DMakefile22 dm-verity-y += dm-verity-target.o
65 obj-$(CONFIG_DM_VERITY) += dm-verity.o
84 dm-verity-objs += dm-verity-fec.o
88 dm-verity-objs += dm-verity-verify-sig.o
DKconfig504 be called dm-verity.
514 Add ability for dm-verity device to be validated if the
526 Add forward error correction support to dm-verity. This option
/Linux-v5.4/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.
101 verity <dev> is encrypted the <fec_dev> should be too.
118 rather than every time. This reduces the overhead of dm-verity so that it
138 dm-verity is meant to be set up as part of a verified boot path. This
142 When a dm-verity device is configured, it is expected that the caller
190 The verity kernel code does not read the verity metadata on-disk header.
193 verity header.
218 "0 2097152 verity 1 /dev/sda1 /dev/sda2 4096 4096 262144 1 sha256 "\
Dindex.rst33 verity
/Linux-v5.4/fs/f2fs/
DMakefile11 f2fs-$(CONFIG_FS_VERITY) += verity.o
Dsysfs.c499 F2FS_FEATURE_RO_ATTR(verity, FEAT_VERITY);
568 ATTR_LIST(verity),
Df2fs.h3600 F2FS_FEATURE_FUNCS(verity, VERITY);
/Linux-v5.4/fs/ext4/
DMakefile16 ext4-$(CONFIG_FS_VERITY) += verity.o
Dsysfs.c246 EXT4_ATTR_FEATURE(verity);
261 ATTR_LIST(verity),
Dinode.c1412 bool verity = ext4_verity_in_progress(inode); in ext4_write_end() local
1434 if (!verity) in ext4_write_end()
1439 if (old_size < pos && !verity) in ext4_write_end()
1450 if (pos + len > inode->i_size && !verity && ext4_can_truncate(inode)) in ext4_write_end()
1461 if (pos + len > inode->i_size && !verity) { in ext4_write_end()
1522 bool verity = ext4_verity_in_progress(inode); in ext4_journalled_write_end() local
1552 if (!verity) in ext4_journalled_write_end()
1559 if (old_size < pos && !verity) in ext4_journalled_write_end()
1568 if (pos + len > inode->i_size && !verity && ext4_can_truncate(inode)) in ext4_journalled_write_end()
1579 if (pos + len > inode->i_size && !verity) { in ext4_journalled_write_end()
Dext4.h1795 EXT4_FEATURE_RO_COMPAT_FUNCS(verity, VERITY) in EXT4_FEATURE_COMPAT_FUNCS()
/Linux-v5.4/security/loadpin/
DKconfig12 dm-verity or a CDROM.
/Linux-v5.4/Documentation/admin-guide/LSM/
DLoadPin.rst8 such as dm-verity or CDROM. This allows systems that have a verified
/Linux-v5.4/fs/
DMakefile37 obj-$(CONFIG_FS_VERITY) += verity/
DKconfig115 source "fs/verity/Kconfig"
/Linux-v5.4/
DMAINTAINERS6727 F: fs/verity/