Home
last modified time | relevance | path

Searched refs:keyslot (Results 1 – 14 of 14) sorted by relevance

/openbmc/estoraged/include/
H A DcryptsetupInterface.hpp85 struct crypt_device* cd, int keyslot, const char* volumeKey,
115 struct crypt_device* cd, const char* name, int keyslot,
136 virtual int cryptKeyslotDestroy(struct crypt_device* cd, int keyslot) = 0;
158 cryptKeySlotStatus(struct crypt_device* cd, int keyslot) = 0;
201 int cryptKeyslotAddByVolumeKey(struct crypt_device* cd, int keyslot, in cryptKeyslotAddByVolumeKey() argument
207 cd, keyslot, volumeKey, volumeKeySize, passphrase, passphraseSize); in cryptKeyslotAddByVolumeKey()
217 struct crypt_device* cd, const char* name, int keyslot, in cryptActivateByPassphrase() argument
220 return crypt_activate_by_passphrase(cd, name, keyslot, passphrase, in cryptActivateByPassphrase()
231 return crypt_keyslot_destroy(cd, keyslot); in cryptKeyslotDestroy()
240 int keyslot) override in cryptKeySlotStatus() argument
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D293.out26 qemu-io: can't open: Invalid password, cannot unlock any keyslot
29 qemu-io: can't open: Invalid password, cannot unlock any keyslot
38 qemu-img: Can't add a keyslot - all keyslots are in use
57 qemu-io: can't open: Invalid password, cannot unlock any keyslot
58 qemu-io: can't open: Invalid password, cannot unlock any keyslot
59 qemu-io: can't open: Invalid password, cannot unlock any keyslot
69 qemu-io: can't open: Invalid password, cannot unlock any keyslot
70 qemu-io: can't open: Invalid password, cannot unlock any keyslot
71 qemu-io: can't open: Invalid password, cannot unlock any keyslot
79 qemu-io: can't open: Invalid password, cannot unlock any keyslot
[all …]
H A D29378 …MG amend $SECRETS $IMGS0 -o ${PR}state=active,${PR}new-secret=sec4,${PR}iter-time=10,${PR}keyslot=4
82 …MG amend $SECRETS $IMGS1 -o ${PR}state=active,${PR}new-secret=sec3,${PR}iter-time=10,${PR}keyslot=3
89 $QEMU_IMG amend $SECRETS $IMGS1 -o ${PR}state=inactive,${PR}keyslot=4 | _filter_img_create
105 $QEMU_IMG amend $SECRETS $IMGS1 -o ${PR}state=inactive,${PR}keyslot=2 | _filter_img_create
171 $QEMU_IMG amend $SECRETS $IMGS0 -o ${PR}state=active,${PR}new-secret=sec1,${PR}keyslot=0
175 … $SECRETS $IMGS0 -o ${PR}state=active,${PR}new-secret=sec1,${PR}iter-time=10,${PR}keyslot=0 --force
186 $QEMU_IMG amend $SECRETS $IMGS1 -o ${PR}state=inactive,${PR}keyslot=0
193 $QEMU_IMG amend $SECRETS $IMGS1 -o ${PR}state=inactive,${PR}keyslot=1 --force
197 $QEMU_IMG amend $SECRETS $IMGS1 -o ${PR}state=inactive,${PR}keyslot=0 --force
H A D29461 $QEMU_IMG amend $SECRETS $IMGS0 -o state=active,new-secret=sec1,keyslot=1,iter-time=10
69 $QEMU_IMG amend $SECRETS $IMGS1 -o state=inactive,keyslot=0 | _filter_img_create
H A D294.out18 qemu-io: can't open: Invalid password, cannot unlock any keyslot
25 qemu-io: can't open: Invalid password, cannot unlock any keyslot
H A D295.out11 Job failed: Invalid password, cannot unlock any keyslot
20 Job failed: Refusing to overwrite active keyslot 2 - please erase it first
H A D188.out17 qemu-io: can't open: Invalid password, cannot unlock any keyslot
H A D082.out690 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
706 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
722 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
738 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
754 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
770 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
786 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
802 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
839 encrypt.keyslot=<num> - Select a single keyslot to modify explicitly
/openbmc/linux/drivers/mmc/core/
H A Dcrypto.c33 struct blk_crypto_keyslot *keyslot; in mmc_crypto_prepare_req() local
40 keyslot = req->crypt_keyslot; in mmc_crypto_prepare_req()
41 if (keyslot) in mmc_crypto_prepare_req()
42 mrq->crypto_key_slot = blk_crypto_keyslot_index(keyslot); in mmc_crypto_prepare_req()
/openbmc/qemu/crypto/
H A Dblock-luks.c1622 int keyslot; in qcrypto_block_luks_amend_add_keyslot() local
1640 keyslot = opts_luks->keyslot; in qcrypto_block_luks_amend_add_keyslot()
1641 if (keyslot < 0 || keyslot >= QCRYPTO_BLOCK_LUKS_NUM_KEY_SLOTS) { in qcrypto_block_luks_amend_add_keyslot()
1649 if (keyslot == -1) { in qcrypto_block_luks_amend_add_keyslot()
1660 keyslot); in qcrypto_block_luks_amend_add_keyslot()
1740 int keyslot = opts_luks->keyslot; in qcrypto_block_luks_amend_erase_keyslots() local
1742 if (keyslot < 0 || keyslot >= QCRYPTO_BLOCK_LUKS_NUM_KEY_SLOTS) { in qcrypto_block_luks_amend_erase_keyslots()
1763 keyslot); in qcrypto_block_luks_amend_erase_keyslots()
1771 keyslot); in qcrypto_block_luks_amend_erase_keyslots()
1780 keyslot); in qcrypto_block_luks_amend_erase_keyslots()
[all …]
/openbmc/estoraged/src/test/include/
H A Destoraged_test.hpp53 (struct crypt_device * cd, int keyslot, const char* volume_key,
70 (struct crypt_device * cd, const char* name, int keyslot,
84 (struct crypt_device * cd, int keyslot), (override));
/openbmc/qemu/qapi/
H A Dcrypto.json385 # keyslot. Currently defaults to 2000.
387 # @keyslot: Optional. ID of the keyslot to activate/deactivate. For
388 # keyslot activation, keyslot should not be active already (this
389 # is unsafe to update an active keyslot), but possible if 'force'
390 # parameter is given. If keyslot is not given, first free keyslot
393 # For keyslot deactivation, this parameter specifies the exact
394 # keyslot to deactivate
406 '*keyslot': 'int',
H A Dblock-core.json5485 # allows erase of the last active keyslot (permanent loss of
5486 # data), and replacement of an active keyslot (possible loss of
/openbmc/linux/Documentation/block/
H A Dinline-encryption.rst21 algorithm, and data unit size first be programmed into a keyslot. Each
22 low-level I/O request then just contains a keyslot index and data unit number.
65 keyslots and reuse an already-programmed keyslot when possible.
105 device drivers need to care about most details of keyslot management.
107 Specifically, for each keyslot, the block layer (via the blk_crypto_profile)
110 ``struct request`` for a bio that has an encryption context, it grabs a keyslot
112 keyslot (a keyslot that isn't in-use by any I/O), then programs the key into the
113 least-recently-used idle keyslot using the function the device driver provided.
130 includes getting a keyslot from the clone's target device if needed.
137 likewise for the block layer's keyslot management logic. It is also desirable
[all …]