Home
last modified time | relevance | path

Searched refs:volume (Results 1 – 18 of 18) sorted by relevance

/systemd-251/src/veritysetup/
Dveritysetup.c139 const char *volume, *data_device, *verity_device, *root_hash, *options; in run() local
147 volume = argv[2]; in run()
153 if (!filename_is_valid(volume)) in run()
154 … return log_error_errno(SYNTHETIC_ERRNO(EINVAL), "Volume name '%s' is not valid.", volume); in run()
166 status = crypt_status(cd, volume); in run()
168 log_info("Volume %s already active.", volume); in run()
206 … r = crypt_activate_by_signed_key(cd, volume, m, l, hash_sig, hash_sig_size, arg_activate_flags); in run()
211 r = crypt_activate_by_volume_key(cd, volume, m, l, arg_activate_flags); in run()
216 const char *volume; in run() local
218 volume = argv[2]; in run()
[all …]
/systemd-251/src/integritysetup/
Dintegritysetup.c91 char *verb, *volume; in run() local
101 volume = argv[2]; in run()
127 if (!filename_is_valid(volume)) in run()
128 … return log_error_errno(SYNTHETIC_ERRNO(EINVAL), "Volume name '%s' is not valid.", volume); in run()
149 status = crypt_status(cd, volume); in run()
151 log_info("Volume %s already active.", volume); in run()
171 … r = crypt_activate_by_volume_key(cd, volume, key_buf, key_buf_size, arg_activate_flags); in run()
180 if (!filename_is_valid(volume)) in run()
181 … return log_error_errno(SYNTHETIC_ERRNO(EINVAL), "Volume name '%s' is not valid.", volume); in run()
183 r = crypt_init_by_name(&cd, volume); in run()
[all …]
/systemd-251/test/units/
Dtestsuite-70.sh16 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headless=1
17 /usr/lib/systemd/systemd-cryptsetup detach test-volume
21 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headless=1 && { echo…
26 env PIN=123456 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headl…
27 /usr/lib/systemd/systemd-cryptsetup detach test-volume
30 env PIN=123457 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headl…
34 env PIN=123456 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headl…
39 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headless=1
40 /usr/lib/systemd/systemd-cryptsetup detach test-volume
44 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headless=1 && exit 1
/systemd-251/src/cryptsetup/
Dcryptsetup.c726 static char *make_bindname(const char *volume) { in make_bindname() argument
729 if (asprintf(&s, "@%" PRIx64"/cryptsetup/%s", random_u64(), volume) < 0) in make_bindname()
1749 const char *volume, *source, *key_file, *options; in run() local
1761 volume = argv[2]; in run()
1766 if (!filename_is_valid(volume)) in run()
1767 … return log_error_errno(SYNTHETIC_ERRNO(EINVAL), "Volume name '%s' is not valid.", volume); in run()
1781 volume, source, strempty(arg_type), strempty(arg_cipher)); in run()
1790 bindname = make_bindname(volume); in run()
1797 fn = strjoina(volume, ".key"); in run()
1806 log_debug("Automatically discovered key for volume '%s'.", volume); in run()
[all …]
/systemd-251/docs/
DHOME_DIRECTORY.md59 second field the encrypted volume key. The latter is encrypted using AES256 in
83 Linux file system inside a LUKS2 volume inside a loopback file (or on removable
91 * This partition must contain a LUKS2 volume, whose label must be the user
92 name. The LUKS2 volume must contain a LUKS2 token field of type
98 encryption used is the same as the LUKS2 volume itself uses, unlocked by the
99 same volume key, but based on its own IV.
101 * Inside of this LUKS2 volume must be a Linux file system, one of `ext4`,
127 directory and a generic storage volume.)
DUSER_RECORD.md358 LUKS volume that is mounted as home directory, and `cifs` a home directory
366 of the file system and LUKS volume, while for the others this likely translates
428 the LUKS volume on. For `fscrypt`, `directory`, `subvolume` this refers to the
460 the LUKS volume UUID the home directory is located in. This is primarily
479 the default mount options for the file system in the LUKS volume.
485 `luksVolumeKeySize` → An unsigned integer, indicating the volume key length in
DDISCOVERABLE_PARTITIONS.md236 Verity volume may be fully automatic: if the root partition's UUID is chosen
241 Verity volume. In this mode a Verity signature partition is not used and
248 and setup of a Verity volume may be fully automatic. First, the specified
DROOT_STORAGE_DAEMONS.md14 A number of complex storage technologies on Linux (e.g. RAID, volume
/systemd-251/src/boot/efi/
Dcpio.c328 EFI_FILE_IO_INTERFACE *volume; in pack_cpio() local
343 &FileSystemProtocol, (void*)&volume); in pack_cpio()
356 err = volume->OpenVolume(volume, &root); in pack_cpio()
/systemd-251/rules.d/
D64-btrfs.rules.in14 # reconsider pending devices in case when multidevice volume awaits
/systemd-251/test/fuzz/fuzz-udev-rules/
D64-btrfs.rules14 # reconsider pending devices in case when multidevice volume awaits
/systemd-251/hwdb.d/
D60-keyboard.hwdb243 # causing the volume-button mappings to be off by one, correct this
369 KEYBOARD_KEY_ae=! # volume down
370 KEYBOARD_KEY_b0=! # volume up
946 # Fix for volume keys on Lenovo Yoga S940
1631 KEYBOARD_KEY_ae=!volumedown # Fn+F7 volume down
1632 KEYBOARD_KEY_b0=!volumeup # Fn+F8 volume up
1714 KEYBOARD_KEY_ae=!volumedown # Fn+F7 volume down
1715 KEYBOARD_KEY_b0=!volumeup # Fn+F8 volume up
1874 KEYBOARD_KEY_ae=! # volume down
1875 KEYBOARD_KEY_b0=! # volume up
[all …]
/systemd-251/shell-completion/bash/
Dhomectl93 --luks-volume-key-size
/systemd-251/
DLICENSE.GPL2130 with the Program (or with a work based on the Program) on a volume of
DLICENSE.LGPL2.1207 with the Library (or with a work based on the Library) on a volume of
DTODO1590 so that mounts propagate down but not up - eg, user A setting up a backup volume
1602 unlock the volume in order to create the first user and add the first pw.
DNEWS470 enter a PIN when using TPM-based unlocking of a volume via the new
1681 and formatted on a LUKS-encrypted volume whose key is generated
2053 format "volume-name data-device hash-device roothash options",
2449 even if the root fs of the system is not itself a btrfs volume.
3630 volume activation was successful or not. This is useful if the key
3636 unlock the volume with an empty password. This is useful for
3642 /etc/cryptsetup-keys.d/<volume>.key and
3643 /run/cryptsetup-keys.d/<volume>.key, if any of these files exist.
3981 set, the specified encrypted volume is unlocked already in the
/systemd-251/LICENSES/
DLGPL-2.0-or-later.txt74 … the Library with the Library (or with a work based on the Library) on a volume of a storage or di…