Home
last modified time | relevance | path

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

12345

/linux/security/integrity/
H A 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_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
18 integrity-$(CONFIG_LOAD_PPC_KEYS) += platform_certs/efi_parser.o \
H A DKconfig8 This option enables the integrity subsystem, which is comprised
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)
128 1 - additional integrity auditing messages
130 Additional informational integrity auditing messages would
134 source "security/integrity/ima/Kconfig"
135 source "security/integrity/evm/Kconfig"
/linux/Documentation/admin-guide/device-mapper/
H A 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 …]
H A Ddm-crypt.rst137 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 Ddm-ima.rst15 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 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
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/Documentation/block/
H A 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 …]
H A Dindex.rst14 data-integrity
/linux/include/linux/
H A Dt10-pi.h45 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 Ddata-integrity.rst4 :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）。
H A Dindex.rst20 data-integrity
/linux/Documentation/ABI/stable/
H A Dsysfs-class-tpm4 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/Documentation/security/
H A Dipe.rst17 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.
57 initially, passing the required integrity check. Then, on the page fault
[all …]
H A Dsnp-tdx-threat-model.rst26 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.
H A Ddigsig.rst20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
70 * Verifies data integrity against digital signature.
/linux/tools/testing/selftests/net/
H A Dtcp_mmap.c89 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/staging/
H A Dxz.rst13 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/block/
H A Dt10-pi.c127 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()
H A Dblk-integrity.c200 return &dev_to_disk(dev)->queue->limits.integrity; in dev_to_bi()
241 lim.integrity.flags &= ~flag; in flag_store()
243 lim.integrity.flags |= flag; in flag_store()
H A Dblk-settings.c135 (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()
570 if (q->crypto_profile && lim->integrity.tag_size) { in queue_limits_commit_update()
988 struct blk_integrity *ti = &t->integrity; in queue_limits_stack_integrity()
989 struct blk_integrity *bi = &b->integrity; in queue_limits_stack_integrity()
/linux/security/integrity/evm/
H A DKconfig13 integrity attacks.
57 /sys/kernel/security/integrity/evm/evm_xattrs.
68 verify EVM integrity starting from the 'init' process. The
/linux/security/integrity/ima/
H A DKconfig26 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 appraisal refer to:
/linux/Documentation/admin-guide/
H A Djfs.rst28 from backup media. The integrity of the volume is not
31 integrity(*)
/linux/Documentation/translations/zh_CN/filesystems/
H A Dubifs-authentication.rst32 基于 Linux 块 IO 层的 dm-crypt 等文件系统，可通过 dm-integrity 或
348 [DM-INTEGRITY] https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.rst
/linux/arch/powerpc/configs/
H A Dsecurity.config3 # This is the equivalent of booting with lockdown=integrity

12345