| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 2 Data Integrity 16 protocols (SBC Data Integrity Field, SCC protection proposal) as well 18 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 35 2. The Data Integrity Extensions 40 allow the operating system to interact with the integrity metadata 45 The SCSI Data Integrity Field works by appending 8 bytes of protection 46 information to each sector. The data + integrity metadata is stored 53 encouraged them to allow separation of the data and integrity metadata [all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H 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. 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 …]
|
| H A D | dm-crypt.rst | 137 integrity:<bytes>:<type> 139 in per-bio integrity structure. This metadata must by provided 140 by underlying dm-integrity target. 146 integrity for the encrypted device. The additional space is then 150 Optionally set the integrity key size if it differs from the digest size. 169 Use an integrity key of <bytes> size instead of using an integrity key size
|
| H 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 …]
|
| H A D | verity.rst | 5 Device-Mapper's "verity" target provides transparent integrity checking of 32 This is the device containing data, the integrity of which needs to be 178 Cryptographic hashes are used to assert the integrity of the device on a 186 integrity checking is essential. 221 It is expected that a user-space tool will verify the integrity of the
|
| /linux/security/integrity/ |
| H A D | Makefile | 3 # Makefile for caching inode integrity data (iint) 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_INTEGRITY_MACHINE_KEYRING) += platform_certs/machine_keyring.o 14 integrity-$(CONFIG_LOAD_UEFI_KEYS) += platform_certs/efi_parser.o \ 17 integrity-$(CONFIG_LOAD_IPL_KEYS) += platform_certs/load_ipl_s390.o [all …]
|
| H A D | Kconfig | 3 config INTEGRITY config 4 bool "Integrity subsystem" 8 This option enables the integrity subsystem, which is comprised 9 of a number of different components including the Integrity 17 if INTEGRITY 47 bool "Require all keys on the integrity keyrings be signed" 120 bool "Enables integrity auditing support " 124 In addition to enabling integrity auditing support, this 126 controls the level of integrity auditing messages. 127 0 - basic integrity auditing messages (default) [all …]
|
| H A D | iint.c | 9 * - initialize the integrity directory in securityfs 13 #include "integrity.h" 32 * integrity_load_keys - load integrity keys hook 50 integrity_dir = securityfs_create_dir("integrity", NULL); in integrity_fs_init() 55 pr_err("Unable to create integrity sysfs dir: %d\n", in integrity_fs_init()
|
| /linux/Documentation/security/ |
| H A D | ipe.rst | 3 Integrity Policy Enforcement (IPE) - Kernel Documentation 17 strong integrity guarantees over both the executable code, and specific 19 specific data files would not be readable unless they passed integrity 22 of what would provide the integrity claims. At the time, there were two 23 main mechanisms considered that could guarantee integrity for the system 30 over IMA+EVM as the *integrity mechanism* in the original use case of IPE 39 files), cannot be enforced to be globally integrity verified. This means 41 enforce the integrity policy, or it should not. 44 policy would indicate what labels required integrity verification, which 48 file should be subject to integrity policy. [all …]
|
| H A D | snp-tdx-threat-model.rst | 26 security technologies that aim to protect the confidentiality and integrity 46 integrity for the VM's guest memory and execution state (vCPU registers), 51 …w.amd.com/system/files/techdocs/sev-snp-strengthening-vm-isolation-with-integrity-protection-and-m… 163 integrity protection. This threat model assumes that those features are 168 1. Preserve the confidentiality and integrity of CoCo guest's private 201 data should also be considered untrusted until its integrity and 226 This allows the host to break the integrity of the code running 233 integrity or freshness of such data.
|
| /linux/block/ |
| H A D | bio-integrity-auto.c | 6 * Automatically generate and verify integrity data on PI capable devices if the 8 * data integrity even if the file system (or other user of the block device) is 11 #include <linux/blk-integrity.h> 62 pr_warn_once("%s: unknown integrity checksum type:%d\n", in bi_offload_capable() 71 * __bio_integrity_endio - Integrity I/O completion function 75 * integrity is a time-consuming task which must be run in process context. 97 * bio_integrity_prep - Prepare bio for integrity I/O 100 * Checks if the bio already has an integrity payload attached. If it does, the 103 * Otherwise allocates integrity payload and for writes the integrity metadat [all...] |
| H A D | blk-settings.c | 9 #include <linux/blk-integrity.h> 127 * Maximum size of I/O that needs a block layer integrity buffer. Limited 128 * by the number of intervals for which we can fit the integrity buffer into 135 (BLK_INTEGRITY_MAX_SIZE / lim->integrity.metadata_size) << in max_integrity_io_size() 136 lim->integrity.interval_exp); in max_integrity_io_size() 141 struct blk_integrity *bi = &lim->integrity; in blk_validate_integrity_limits() 154 pr_warn("integrity support disabled.\n"); in blk_validate_integrity_limits() 211 * The block layer automatically adds integrity data for bios that don't in blk_validate_integrity_limits() 213 * metadata segment can cover the integrity data for the entire I/O. in blk_validate_integrity_limits() 566 if (q->crypto_profile && lim->integrity.tag_size) { in queue_limits_commit_update() [all …]
|
| H A D | blk-mq-dma.c | 5 #include <linux/blk-integrity.h> 319 * blk_rq_integrity_dma_map_iter_start - map the first integrity DMA segment 326 * Start DMA mapping @req integrity data to @dma_dev. @state and @iter are 345 unsigned len = bio_integrity_bytes(&req->q->limits.integrity, in blk_rq_integrity_dma_map_iter_start() 360 * blk_rq_integrity_dma_map_iter_next - map the next integrity DMA segment for 367 * Iterate to the next integrity mapping after a previous call to 393 * blk_rq_map_integrity_sg - Map integrity metadata into a scatterlist 397 * Description: Map the integrity vectors in request into a 429 * is bigger than number of req's physical integrity segments in blk_rq_map_integrity_sg()
|
| H A D | t10-pi.c | 8 #include <linux/blk-integrity.h> 127 struct blk_integrity *bi = &rq->q->limits.integrity; in t10_pi_type1_prepare() 178 struct blk_integrity *bi = &rq->q->limits.integrity; in t10_pi_type1_complete() 301 struct blk_integrity *bi = &rq->q->limits.integrity; in ext_pi_type1_prepare() 341 struct blk_integrity *bi = &rq->q->limits.integrity; in ext_pi_type1_complete() 451 struct blk_integrity *bi = &rq->q->limits.integrity; in blk_integrity_prepare() 464 struct blk_integrity *bi = &rq->q->limits.integrity; in blk_integrity_complete()
|
| /linux/Documentation/ABI/stable/ |
| H 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/security/integrity/ima/ |
| H A D | Kconfig | 2 # IBM Integrity Measurement Architecture 5 bool "Integrity Measurement Architecture(IMA)" 18 The Trusted Computing Group(TCG) runtime Integrity 26 an aggregate integrity value over this list inside the 53 that IMA uses to maintain the integrity aggregate of the 88 prompt "Default integrity hash algorithm" 92 list, integrity appraisal and audit log. The compiled default 145 bool "Appraise integrity measurements" 148 This option enables local measurement integrity appraisal. 154 For more information on integrity appraisa [all...] |
| H A D | ima_main.c | 3 * Integrity Measurement Architecture 480 * On success return 0. On integrity appraisal error, assuming the file 517 * this point. Eliminate this integrity gap by denying the mprotect 578 * On success return 0. On integrity appraisal error, assuming the file 608 * On success return 0. On integrity appraisal error, assuming the file 625 * and appraise the integrity of a file to be executed by script interpreters. 626 * Unlike any of the other LSM hooks where the kernel enforces file integrity, 627 * enforcing file integrity is left up to the discretion of the script 630 * On success return 0. On integrity appraisal error, assuming the file 655 * On success return 0. On integrity appraisal error, assuming the file [all …]
|
| /linux/Documentation/staging/ |
| H A D | xz.rst | 13 for executable code. CRC32 is supported for integrity checking. 53 Since the XZ Embedded supports only streams with CRC32 or no integrity 54 check, make sure that you don't use some other integrity check type 62 which will verify the integrity of the uncompressed data anyway. 63 Double checking the integrity would probably be waste of CPU cycles. 65 by the decoder; you can only change the integrity check type (or
|
| /linux/include/linux/ |
| H A D | t10-pi.h | 45 rq->q->limits.integrity.interval_exp) in t10_pi_ref_tag() 46 shift = rq->q->limits.integrity.interval_exp; in t10_pi_ref_tag() 70 rq->q->limits.integrity.interval_exp) in ext_pi_ref_tag() 71 shift = rq->q->limits.integrity.interval_exp; in ext_pi_ref_tag()
|
| /linux/Documentation/translations/zh_CN/block/ |
| H A D | data-integrity.rst | 4 :Original: Documentation/block/data-integrity.rst 117 块设备可以在 queue_limits 结构中的 integrity 子结构中设置完整性信息。 135 /sys/block/<bdev>/integrity/write_generate 139 /sys/block/<bdev>/integrity/read_verify 170 integrity bio_vec list 中存储多少页保护数据(类似 bio_alloc)。
|
| /linux/drivers/md/ |
| H A D | dm-io-rewind.c | 8 #include <linux/blk-integrity.h> 48 * dm_bio_integrity_rewind - Rewind integrity vector 49 * @bio: bio whose integrity vector to update 52 * Description: This function calculates how many integrity bytes the 54 * integrity vector accordingly.
|
| /linux/security/integrity/evm/ |
| H A D | Kconfig | 13 integrity attacks. 57 /sys/kernel/security/integrity/evm/evm_xattrs. 68 verify EVM integrity starting from the 'init' process. The
|
| /linux/drivers/scsi/ |
| H A D | sd_dif.c | 3 * sd_dif.c - SCSI Data Integrity Field 9 #include <linux/blk-integrity.h> 31 struct blk_integrity *bi = &lim->integrity; in sd_dif_config_host()
|
| /linux/tools/testing/selftests/net/ |
| H A D | tcp_mmap.c | 89 static int integrity; /* -i option: sender and receiver compute sha256 over the data.*/ variable 205 if (integrity) { in child_thread() 233 if (integrity) in child_thread() 249 if (integrity) in child_thread() 268 if (integrity) in child_thread() 280 if (integrity) { in child_thread() 504 integrity = 1; in main() 581 if (integrity) { in main() 601 if (integrity) in main() 605 if (integrity && total == FILE_SZ) { in main()
|
| /linux/Documentation/security/keys/ |
| H A D | trusted-encrypted.rst | 11 convenience, and are integrity verified. 105 * Optional binding to platform integrity state 109 Keys can be optionally sealed to specified PCR (integrity measurement) 110 values, and only unsealed by the TPM, if PCRs and blob integrity 119 Relies on Secure/Trusted boot process for platform integrity. It can 125 for platform integrity. 130 platform integrity. 450 compromised by a user level problem, and when sealed to a platform integrity
|