/linux/security/integrity/ |
A D | Makefile | 6 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 \ 16 integrity-$(CONFIG_LOAD_IPL_KEYS) += platform_certs/load_ipl_s390.o 17 integrity-$(CONFIG_LOAD_PPC_KEYS) += platform_certs/efi_parser.o \
|
A D | Kconfig | 8 This option enables the integrity subsystem, which is comprised 46 bool "Require all keys on the integrity keyrings be signed" 85 bool "Enables integrity auditing support " 89 In addition to enabling integrity auditing support, this 91 controls the level of integrity auditing messages. 92 0 - basic integrity auditing messages (default) 93 1 - additional integrity auditing messages 95 Additional informational integrity auditing messages would 99 source "security/integrity/ima/Kconfig" 100 source "security/integrity/evm/Kconfig"
|
A D | .built-in.a.cmd | 1 …integrity/built-in.a := echo >/dev/null; rm -f security/integrity/built-in.a; /usr/bin/ccache /hom…
|
A D | .integrity_audit.o.cmd | 1 …integrity/integrity_audit.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolc… 3 source_security/integrity/integrity_audit.o := security/integrity/integrity_audit.c 5 deps_security/integrity/integrity_audit.o := \ 935 security/integrity/integrity.h \ 943 include/linux/integrity.h \ 947 security/integrity/integrity_audit.o: $(deps_security/integrity/integrity_audit.o) 949 $(deps_security/integrity/integrity_audit.o):
|
A D | .iint.o.cmd | 1 …integrity/iint.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch… 3 source_security/integrity/iint.o := security/integrity/iint.c 5 deps_security/integrity/iint.o := \ 924 security/integrity/integrity.h \ 931 include/linux/integrity.h \ 969 security/integrity/iint.o: $(deps_security/integrity/iint.o) 971 $(deps_security/integrity/iint.o):
|
/linux/Documentation/block/ |
A D | data-integrity.rst | 18 support for appending integrity metadata to an I/O. The integrity 40 allow the operating system to interact with the integrity metadata 136 The data integrity patches add a new field to struct bio when 140 containing the integrity metadata and the required housekeeping 164 merging and splitting the integrity metadata. 186 /sys/block/<bdev>/integrity/write_generate 190 /sys/block/<bdev>/integrity/read_verify 229 The integrity payload will be freed at bio_free() time. 237 the integrity metadata in the pages must be in a format 242 integrity metadata must have a value of bip->bip_sector. [all …]
|
/linux/Documentation/admin-guide/device-mapper/ |
A D | dm-integrity.rst | 2 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. 46 3. unload the dm-integrity target 48 5. load the dm-integrity target with the target size 59 dm-integrity won't read of write these sectors 70 and integrity tag doesn't match. 72 data and integrity tags are written to the 127 generate and verify the integrity tags. 215 1. the number of integrity mismatches [all …]
|
A D | dm-ima.rst | 15 target types like crypt, verity, integrity etc. Each of these target 49 /sys/kernel/security/integrity/ima/ascii_runtime_measurements 50 /sys/kernel/security/integrity/ima/binary_runtime_measurements 62 TEMPLATE_NAME := Template name that registered the integrity value (e.g. ima-buf). 143 target_name := Name of the target. 'linear', 'crypt', 'integrity' etc. 331 #. integrity 418 3. integrity 421 section above) has the following data format for 'integrity' target. 430 target_name := "target_name=integrity" 450 When a 'integrity' target is loaded, then IMA ASCII measurement log will have an entry [all …]
|
A D | dm-crypt.rst | 132 integrity:<bytes>:<type> 134 in per-bio integrity structure. This metadata must by provided 135 by underlying dm-integrity target. 141 integrity for the encrypted device. The additional space is then
|
/linux/Documentation/ABI/stable/ |
A D | sysfs-class-tpm | 4 Contact: linux-integrity@vger.kernel.org 12 Contact: linux-integrity@vger.kernel.org 24 Contact: linux-integrity@vger.kernel.org 32 Contact: linux-integrity@vger.kernel.org 49 Contact: linux-integrity@vger.kernel.org 72 Contact: linux-integrity@vger.kernel.org 81 Contact: linux-integrity@vger.kernel.org 89 Contact: linux-integrity@vger.kernel.org 112 Contact: linux-integrity@vger.kernel.org 164 Contact: linux-integrity@vger.kernel.org [all …]
|
/linux/block/ |
A D | blk-integrity.c | 123 struct blk_integrity *b1 = &gd1->queue->integrity; in blk_integrity_compare() 124 struct blk_integrity *b2 = &gd2->queue->integrity; in blk_integrity_compare() 225 struct blk_integrity *bi = &disk->queue->integrity; in integrity_attr_show() 237 struct blk_integrity *bi = &disk->queue->integrity; in integrity_attr_store() 352 ATTRIBUTE_GROUPS(integrity); 399 struct blk_integrity *bi = &disk->queue->integrity; in blk_integrity_register() 429 struct blk_integrity *bi = &disk->queue->integrity; in blk_integrity_unregister()
|
A D | built-in.a | 38 bio-integrity.o/ 39 blk-integrity.o/
|
A D | t10-pi.c | 135 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_type1_prepare() 184 unsigned intervals = nr_bytes >> rq->q->integrity.interval_exp; in t10_pi_type1_complete() 185 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_type1_complete()
|
A D | .built-in.a.cmd | 1 …cgroup.o block/mq-deadline.o block/kyber-iosched.o block/bio-integrity.o block/blk-integrity.o blo…
|
A D | Makefile | 28 obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o
|
/linux/include/linux/ |
A D | t10-pi.h | 45 if (rq->q->integrity.interval_exp) in t10_pi_ref_tag() 46 shift = rq->q->integrity.interval_exp; in t10_pi_ref_tag()
|
A D | blk-integrity.h | 47 struct blk_integrity *bi = &disk->queue->integrity; in blk_get_integrity() 64 return q->integrity.profile; in blk_integrity_queue_supports_integrity()
|
/linux/Documentation/ABI/testing/ |
A D | sysfs-block | 69 What: /sys/block/<disk>/integrity/format 73 Metadata format for integrity capable block device. 77 What: /sys/block/<disk>/integrity/read_verify 82 integrity of read requests serviced by devices that 83 support sending integrity metadata. 86 What: /sys/block/<disk>/integrity/tag_size 90 Number of bytes of integrity tag space available per 99 integrity metadata. Set if the device is T10 PI-capable. 106 by one integrity tuple. Typically the device's logical 109 What: /sys/block/<disk>/integrity/write_generate [all …]
|
/linux/security/integrity/evm/ |
A D | Kconfig | 12 integrity attacks. 56 /sys/kernel/security/integrity/evm/evm_xattrs. 67 verify EVM integrity starting from the 'init' process.
|
/linux/Documentation/staging/ |
A D | xz.rst | 16 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
|
/linux/security/ |
A D | built-in.a | 30 integrity/iint.o/ 31 integrity/integrity_audit.o/
|
A D | Kconfig | 232 source "security/integrity/Kconfig" 270 …default "landlock,lockdown,yama,loadpin,safesetid,integrity,smack,selinux,tomoyo,apparmor,bpf" if … 271 …default "landlock,lockdown,yama,loadpin,safesetid,integrity,apparmor,selinux,smack,tomoyo,bpf" if … 272 default "landlock,lockdown,yama,loadpin,safesetid,integrity,tomoyo,bpf" if DEFAULT_SECURITY_TOMOYO 273 default "landlock,lockdown,yama,loadpin,safesetid,integrity,bpf" if DEFAULT_SECURITY_DAC 274 default "landlock,lockdown,yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor,bpf"
|
/linux/security/integrity/ima/ |
A D | Kconfig | 25 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 151 bool "Appraise integrity measurements" 155 This option enables local measurement integrity appraisal. 161 For more information on integrity appraisal refer to:
|
/linux/fs/btrfs/ |
A D | Kconfig | 53 bool "Btrfs with integrity check tool compiled in (DANGEROUS)" 62 If the integrity check tool is included and activated in 68 to verify the integrity of (super)-block write requests
|
/linux/Documentation/security/ |
A D | digsig.rst | 20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem. 70 * Verifies data integrity against digital signature.
|