Home
last modified time | relevance | path

Searched refs:integrity (Results 1 – 25 of 91) sorted by relevance

1234

/Linux-v4.19/Documentation/device-mapper/
Ddm-integrity.txt1 The dm-integrity target emulates a block device that has additional
2 per-sector tags that can be used for storing integrity information.
4 A general problem with storing integrity tags with every sector is that
5 writing the sector and the integrity tag must be atomic - i.e. in case of
6 crash, either both sector and integrity tag or none of them is written.
8 To guarantee write atomicity, the dm-integrity target uses journal, it
9 writes sector data and integrity tags into a journal, commits the journal
10 and then copies the data and integrity tags to their respective location.
12 The dm-integrity target can be used with the dm-crypt target - in this
13 situation the dm-crypt target creates the integrity data and passes them
[all …]
Ddm-crypt.txt113 integrity:<bytes>:<type>
115 in per-bio integrity structure. This metadata must by provided
116 by underlying dm-integrity target.
122 integrity for the encrypted device. The additional space is then
Dverity.txt4 Device-Mapper's "verity" target provides transparent integrity checking of
28 This is the device containing data, the integrity of which needs to be
138 Cryptographic hashes are used to assert the integrity of the device on a
146 integrity checking is essential.
179 It is expected that a user-space tool will verify the integrity of the
/Linux-v4.19/Documentation/block/
Ddata-integrity.txt14 support for appending integrity metadata to an I/O. The integrity
25 DIF and the other integrity extensions is that the protection format
27 integrity of the I/O and reject it if corruption is detected. This
36 allow the operating system to interact with the integrity metadata
42 information to each sector. The data + integrity metadata is stored
49 encouraged them to allow separation of the data and integrity metadata
63 when writing and vice versa. This allows the integrity metadata to be
69 buffers and the integrity metadata. These two distinct buffers must
72 The separation of the data and integrity metadata buffers as well as
81 The data integrity framework in Linux enables protection information
[all …]
D00-INDEX15 data-integrity.txt
16 - Block data integrity
/Linux-v4.19/security/integrity/
DMakefile6 obj-$(CONFIG_INTEGRITY) += integrity.o
8 integrity-y := iint.o
9 integrity-$(CONFIG_INTEGRITY_AUDIT) += integrity_audit.o
10 integrity-$(CONFIG_INTEGRITY_SIGNATURE) += digsig.o
11 integrity-$(CONFIG_INTEGRITY_ASYMMETRIC_KEYS) += digsig_asymmetric.o
DKconfig7 This option enables the integrity subsystem, which is comprised
45 bool "Require all keys on the integrity keyrings be signed"
55 bool "Enables integrity auditing support "
59 In addition to enabling integrity auditing support, this
61 controls the level of integrity auditing messages.
62 0 - basic integrity auditing messages (default)
63 1 - additional integrity auditing messages
65 Additional informational integrity auditing messages would
69 source security/integrity/ima/Kconfig
70 source security/integrity/evm/Kconfig
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-block31 What: /sys/block/<disk>/integrity/format
35 Metadata format for integrity capable block device.
39 What: /sys/block/<disk>/integrity/read_verify
44 integrity of read requests serviced by devices that
45 support sending integrity metadata.
48 What: /sys/block/<disk>/integrity/tag_size
52 Number of bytes of integrity tag space available per
56 What: /sys/block/<disk>/integrity/device_is_integrity_capable
61 integrity metadata. Set if the device is T10 PI-capable.
63 What: /sys/block/<disk>/integrity/protection_interval_bytes
[all …]
Devm6 against integrity attacks. The initial method maintains an
57 dracut (via 97masterkey and 98integrity) and systemd (via
61 What: security/integrity/evm/evm_xattrs
/Linux-v4.19/block/
Dblk-integrity.c145 struct blk_integrity *b1 = &gd1->queue->integrity; in blk_integrity_compare()
146 struct blk_integrity *b2 = &gd2->queue->integrity; in blk_integrity_compare()
249 struct blk_integrity *bi = &disk->queue->integrity; in integrity_attr_show()
261 struct blk_integrity *bi = &disk->queue->integrity; in integrity_attr_store()
411 struct blk_integrity *bi = &disk->queue->integrity; in blk_integrity_register()
435 memset(&disk->queue->integrity, 0, sizeof(struct blk_integrity)); in blk_integrity_unregister()
DMakefile31 obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o t10-pi.o
Dt10-pi.c203 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_prepare()
262 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_complete()
/Linux-v4.19/security/
DMakefile31 subdir-$(CONFIG_INTEGRITY) += integrity
32 obj-$(CONFIG_INTEGRITY) += integrity/
/Linux-v4.19/security/integrity/evm/
DKconfig11 integrity attacks.
55 /sys/kernel/security/integrity/evm/evm_xattrs.
66 verify EVM integrity starting from the 'init' process.
/Linux-v4.19/Documentation/
Dxz.txt16 for integrity checking. The home page of XZ Embedded is at
59 Since the XZ Embedded supports only streams with no integrity check or
60 CRC32, make sure that you don't use some other integrity check type
67 which will verify the integrity of the uncompressed data anyway.
68 Double checking the integrity would probably be waste of CPU cycles.
70 by the decoder; you can only change the integrity check type (or
Ddigsig.txt20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
70 * Verifies data integrity against digital signature.
/Linux-v4.19/security/integrity/ima/
DKconfig25 an aggregate integrity value over this list inside the
51 that IMA uses to maintain the integrity aggregate of the
90 prompt "Default integrity hash algorithm"
95 list, integrity appraisal and audit log. The compiled default
146 bool "Appraise integrity measurements"
150 This option enables local measurement integrity appraisal.
156 For more information on integrity appraisal refer to:
/Linux-v4.19/fs/btrfs/
DKconfig45 bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
54 If the integrity check tool is included and activated in
60 to verify the integrity of (super)-block write requests
DMakefile16 btrfs-$(CONFIG_BTRFS_FS_CHECK_INTEGRITY) += check-integrity.o
/Linux-v4.19/include/linux/
Dt10-pi.h44 (rq->q->integrity.interval_exp - 9) & 0xffffffff; in t10_pi_ref_tag()
/Linux-v4.19/Documentation/filesystems/
Djfs.txt22 from backup media. The integrity of the volume is not
25 integrity(*) Commit metadata changes to the journal. Use this option to
/Linux-v4.19/Documentation/lightnvm/
Dpblk.txt9 - Maintain the integrity and consistency of the L2P table as well as its
/Linux-v4.19/Documentation/security/keys/
Dtrusted-encrypted.rst11 in hex ascii for convenience, and are integrity verified.
15 (integrity measurement) values, and only unsealed by the TPM, if PCRs and blob
16 integrity verifications match. A loaded Trusted Key can be updated with new
/Linux-v4.19/Documentation/filesystems/nfs/
Drpc-server-gss.txt33 - integrity/privacy protection (signing and encrypting of individual
39 Therefore, we perform per-packet integrity and privacy protection in the
/Linux-v4.19/lib/xz/
DKconfig6 the .xz file format as the container. For integrity checking,

1234