CONFIG_DM_VERITY: Verity target support

General informations

The Linux kernel configuration item CONFIG_DM_VERITY has multiple definitions:

Verity target support found in drivers/md/Kconfig

The configuration item CONFIG_DM_VERITY:

• prompt: Verity target support
• type: tristate
• depends on: CONFIG_BLK_DEV_DM
• defined in drivers/md/Kconfig
• found in Linux kernels: 3.9–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.11, 6.12-rc+HEAD
• modules built: dm-verity

Help text

This device-mapper target creates a read-only device that transparently validates the data on one underlying device against a pre-generated tree of cryptographic checksums stored on a second device.

You'll need to activate the digests you're going to use in the cryptoapi configuration.

To compile this code as a module, choose M here: the module will be called dm-verity.

If unsure, say N.

Verity target support (EXPERIMENTAL) found in drivers/md/Kconfig

The configuration item CONFIG_DM_VERITY:

• prompt: Verity target support (EXPERIMENTAL)
• type: tristate
• depends on: CONFIG_BLK_DEV_DM && CONFIG_EXPERIMENTAL
• defined in drivers/md/Kconfig
• found in Linux kernels: 3.4–3.8
• modules built: dm-verity

Help text

This device-mapper target creates a read-only device that transparently validates the data on one underlying device against a pre-generated tree of cryptographic checksums stored on a second device.

You'll need to activate the digests you're going to use in the cryptoapi configuration.

To compile this code as a module, choose M here: the module will be called dm-verity.

If unsure, say N.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module dm-verity CONFIG_DM_VERITY : drivers/md/Kconfig : "Verity target support" # in 3.4–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.11, 6.12-rc+HEAD

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: