Home
last modified time | relevance | path

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

12345

/Linux-v5.4/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
12 integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o
13 integrity-$(CONFIG_LOAD_UEFI_KEYS) += platform_certs/efi_parser.o \
15 integrity-$(CONFIG_LOAD_IPL_KEYS) += platform_certs/load_ipl_s390.o
DKconfig8 This option enables the integrity subsystem, which is comprised
46 bool "Require all keys on the integrity keyrings be signed"
76 bool "Enables integrity auditing support "
80 In addition to enabling integrity auditing support, this
82 controls the level of integrity auditing messages.
83 0 - basic integrity auditing messages (default)
84 1 - additional integrity auditing messages
86 Additional informational integrity auditing messages would
90 source "security/integrity/ima/Kconfig"
91 source "security/integrity/evm/Kconfig"
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-integrity.rst2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
8 A general problem with storing integrity tags with every sector is that
9 writing the sector and the integrity tag must be atomic - i.e. in case of
10 crash, either both sector and integrity tag or none of them is written.
12 To guarantee write atomicity, the dm-integrity target uses journal, it
13 writes sector data and integrity tags into a journal, commits the journal
14 and then copies the data and integrity tags to their respective location.
16 The dm-integrity target can be used with the dm-crypt target - in this
[all …]
Ddm-crypt.rst124 integrity:<bytes>:<type>
126 in per-bio integrity structure. This metadata must by provided
127 by underlying dm-integrity target.
133 integrity for the encrypted device. The additional space is then
Dindex.rst14 dm-integrity
Dverity.rst5 Device-Mapper's "verity" target provides transparent integrity checking of
32 This is the device containing data, the integrity of which needs to be
149 Cryptographic hashes are used to assert the integrity of the device on a
157 integrity checking is essential.
192 It is expected that a user-space tool will verify the integrity of the
/Linux-v5.4/Documentation/block/
Ddata-integrity.rst18 support for appending integrity metadata to an I/O. The integrity
29 DIF and the other integrity extensions is that the protection format
31 integrity of the I/O and reject it if corruption is detected. This
40 allow the operating system to interact with the integrity metadata
46 information to each sector. The data + integrity metadata is stored
53 encouraged them to allow separation of the data and integrity metadata
67 when writing and vice versa. This allows the integrity metadata to be
73 buffers and the integrity metadata. These two distinct buffers must
76 The separation of the data and integrity metadata buffers as well as
85 The data integrity framework in Linux enables protection information
[all …]
Dindex.rst15 data-integrity
/Linux-v5.4/block/
Dblk-integrity.c123 struct blk_integrity *b1 = &gd1->queue->integrity; in blk_integrity_compare()
124 struct blk_integrity *b2 = &gd2->queue->integrity; in blk_integrity_compare()
227 struct blk_integrity *bi = &disk->queue->integrity; in integrity_attr_show()
239 struct blk_integrity *bi = &disk->queue->integrity; in integrity_attr_store()
354 ATTRIBUTE_GROUPS(integrity);
401 struct blk_integrity *bi = &disk->queue->integrity; in blk_integrity_register()
425 memset(&disk->queue->integrity, 0, sizeof(struct blk_integrity)); in blk_integrity_unregister()
DMakefile29 obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o t10-pi.o
Dt10-pi.c134 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_type1_prepare()
185 unsigned intervals = nr_bytes >> rq->q->integrity.interval_exp; in t10_pi_type1_complete()
186 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_type1_complete()
DKconfig65 bool "Block layer data integrity support"
70 data integrity option provides hooks which can be used by
71 filesystems to ensure better data integrity.
/Linux-v5.4/include/linux/
Dt10-pi.h45 if (rq->q->integrity.interval_exp) in t10_pi_ref_tag()
46 shift = rq->q->integrity.interval_exp; in t10_pi_ref_tag()
/Linux-v5.4/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-v5.4/security/
DMakefile35 subdir-$(CONFIG_INTEGRITY) += integrity
36 obj-$(CONFIG_INTEGRITY) += integrity/
DKconfig242 source "security/integrity/Kconfig"
280 …default "lockdown,yama,loadpin,safesetid,integrity,smack,selinux,tomoyo,apparmor" if DEFAULT_SECUR…
281 …default "lockdown,yama,loadpin,safesetid,integrity,apparmor,selinux,smack,tomoyo" if DEFAULT_SECUR…
282 default "lockdown,yama,loadpin,safesetid,integrity,tomoyo" if DEFAULT_SECURITY_TOMOYO
283 default "lockdown,yama,loadpin,safesetid,integrity" if DEFAULT_SECURITY_DAC
284 default "lockdown,yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor"
/Linux-v5.4/security/integrity/evm/
DKconfig12 integrity attacks.
56 /sys/kernel/security/integrity/evm/evm_xattrs.
67 verify EVM integrity starting from the 'init' process.
/Linux-v5.4/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-v5.4/security/integrity/ima/
DKconfig26 an aggregate integrity value over this list inside the
52 that IMA uses to maintain the integrity aggregate of the
91 prompt "Default integrity hash algorithm"
96 list, integrity appraisal and audit log. The compiled default
147 bool "Appraise integrity measurements"
151 This option enables local measurement integrity appraisal.
157 For more information on integrity appraisal refer to:
/Linux-v5.4/fs/btrfs/
DKconfig47 bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
56 If the integrity check tool is included and activated in
62 to verify the integrity of (super)-block write requests
/Linux-v5.4/Documentation/admin-guide/
Djfs.rst28 from backup media. The integrity of the volume is not
31 integrity(*)
/Linux-v5.4/Documentation/driver-api/
Dlightnvm-pblk.rst9 - Maintain the integrity and consistency of the L2P table as well as its
/Linux-v5.4/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

12345