Home
last modified time | relevance | path

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

12345678910

/OK3568_Linux_fs/kernel/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_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 \
H A DKconfig8 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"
/OK3568_Linux_fs/kernel/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.rst132 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
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
153 Cryptographic hashes are used to assert the integrity of the device on a
161 integrity checking is essential.
196 It is expected that a user-space tool will verify the integrity of the
/OK3568_Linux_fs/kernel/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 Dinline-encryption.rst101 bounce bio as if it were not encrypted at all (except when blk-integrity is
235 Interaction between inline encryption and blk integrity
243 its integrity information is calculated (using the plaintext data, since
245 integrity info is sent to the device. Obviously, the integrity info must be
247 must not store the integrity info that it received with the plaintext data
249 re-generate the integrity info from the ciphertext data and store that on disk
250 instead. Another issue with storing the integrity info of the plaintext data is
253 if the fallback is used, the device will receive the integrity info of the
258 and disallow the combination for now. Whenever a device supports integrity, the
/OK3568_Linux_fs/kernel/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 …]
/OK3568_Linux_fs/kernel/block/
H A 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()
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()
H A Dt10-pi.c135 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_type1_prepare()
186 unsigned intervals = nr_bytes >> rq->q->integrity.interval_exp; in t10_pi_type1_complete()
187 const int tuple_sz = rq->q->integrity.tuple_size; in t10_pi_type1_complete()
H A DMakefile31 obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-block41 What: /sys/block/<disk>/integrity/format
45 Metadata format for integrity capable block device.
49 What: /sys/block/<disk>/integrity/read_verify
54 integrity of read requests serviced by devices that
55 support sending integrity metadata.
58 What: /sys/block/<disk>/integrity/tag_size
62 Number of bytes of integrity tag space available per
66 What: /sys/block/<disk>/integrity/device_is_integrity_capable
71 integrity metadata. Set if the device is T10 PI-capable.
73 What: /sys/block/<disk>/integrity/protection_interval_bytes
[all …]
H A Devm6 against integrity attacks. The initial method maintains an
86 dracut (via 97masterkey and 98integrity) and systemd (via
90 What: security/integrity/evm/evm_xattrs
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/fetch2/
H A Dnpmsw.py86 integrity = params.get("integrity", None)
91 if is_semver(version) and integrity:
101 checksum_name, checksum_expected = npm_integrity(integrity)
119 elif version.startswith("http") and integrity:
125 checksum_name, checksum_expected = npm_integrity(integrity)
H A Dnpm.py63 def npm_integrity(integrity): argument
68 algo, value = integrity.split("-", maxsplit=1)
222 integrity = view.get("dist", {}).get("integrity")
225 if integrity is not None:
226 checksum_name, checksum_expected = npm_integrity(integrity)
/OK3568_Linux_fs/kernel/include/linux/
H A 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()
/OK3568_Linux_fs/u-boot/arch/x86/include/asm/fsp/
H A Dfsp_ffs.h51 union ffs_integrity integrity; member
74 union ffs_integrity integrity; member
/OK3568_Linux_fs/kernel/security/
H A DMakefile37 subdir-$(CONFIG_INTEGRITY) += integrity
38 obj-$(CONFIG_INTEGRITY) += integrity/
H A DKconfig234 source "security/integrity/Kconfig"
272 …default "lockdown,yama,loadpin,safesetid,integrity,smack,selinux,tomoyo,apparmor,bpf" if DEFAULT_S…
273 …default "lockdown,yama,loadpin,safesetid,integrity,apparmor,selinux,smack,tomoyo,bpf" if DEFAULT_S…
274 default "lockdown,yama,loadpin,safesetid,integrity,tomoyo,bpf" if DEFAULT_SECURITY_TOMOYO
275 default "lockdown,yama,loadpin,safesetid,integrity,bpf" if DEFAULT_SECURITY_DAC
276 default "lockdown,yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor,bpf"
/OK3568_Linux_fs/kernel/Documentation/staging/
H A Dxz.rst16 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
/OK3568_Linux_fs/kernel/security/integrity/evm/
H A DKconfig12 integrity attacks.
56 /sys/kernel/security/integrity/evm/evm_xattrs.
67 verify EVM integrity starting from the 'init' process.
/OK3568_Linux_fs/kernel/security/integrity/ima/
H A DKconfig25 an aggregate integrity value over this list inside the
51 that IMA uses to maintain the integrity aggregate of the
88 prompt "Default integrity hash algorithm"
93 list, integrity appraisal and audit log. The compiled default
149 bool "Appraise integrity measurements"
153 This option enables local measurement integrity appraisal.
159 For more information on integrity appraisal refer to:
/OK3568_Linux_fs/kernel/fs/btrfs/
H A DKconfig53 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
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-support/debsums/
H A Ddebsums_2.2.2.bb4 MD5 checksums debsums can verify the integrity of installed package files \
7 DESCRIPTION:${PN}-cron = "Cron scripts to control automatic system integrity \
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/mdadm/files/
H A Drun-ptest5 dir=. ./test --keep-going --disable-integrity

12345678910