Home
last modified time | relevance | path

Searched refs:encryption (Results 1 – 10 of 10) sorted by relevance

/systemd-251/docs/
DCREDENTIALS.md46 encryption is supposed to *just* *work*, and requires no manual setup. (That
81 details on credential encryption, see below.
87 decoded unless access to TPM2/encryption key is available.
180 as cryptographic key material. For this kind of data (symmetric) encryption and
182 may be encrypted and authenticated with AES256-GCM. The encryption key can
186 behaviour is to use the combination of both for encryption, thus ensuring that
DUSERDB_AND_DESKTOPS.md35 but most of the time just suspend them instead. Previously, the encryption keys
42 the encryption keys (i.e. the user's login password) need to be reacquired on
DHOME_DIRECTORY.md97 base64-encoded binary initialization vector for the encryption. The
98 encryption used is the same as the LUKS2 volume itself uses, unlocked by the
DUSER_RECORD.md948 key data needs to be available to derive encryption keys from and similar.
/systemd-251/src/basic/linux/
Dbtrfs_tree.h801 __u8 encryption; member
1026 __u8 encryption; member
/systemd-251/hwdb.d/
D20-pci-classes.hwdb582 ID_PCI_SUBCLASS_FROM_DATABASE=Network and computing encryption device
585 ID_PCI_SUBCLASS_FROM_DATABASE=Entertainment encryption device
Dpci.ids6930 6400 MPC190 Security Processor (S1 family, encryption)
8966 10b5 1123 Sectra KK631 encryption board
22298 0001 KK671 Cardbus encryption board
22299 0002 KK672 Cardbus encryption board
34591 8089 PMC-Sierra PM8019 SAS encryption HBA [Series 7He]
35247 00 Network and computing encryption device
35248 10 Entertainment encryption device
D20-pci-vendor-model.hwdb20430 ID_MODEL_FROM_DATABASE=MPC190 Security Processor (S1 family, encryption)
26472 ID_MODEL_FROM_DATABASE=PCI9080 32-bit; 33MHz PCI <-> IOBus Bridge (Sectra KK631 encryption board)
65856 ID_MODEL_FROM_DATABASE=KK671 Cardbus encryption board
65859 ID_MODEL_FROM_DATABASE=KK672 Cardbus encryption board
101622 ID_MODEL_FROM_DATABASE=PMC-Sierra PM8019 SAS encryption HBA [Series 7He]
/systemd-251/
DTODO102 this way we can implement disk encryption policies that bind to specific
105 encryption can then pass the signature to the TPM to unlock their secrets.
521 what must be read-only, what requires encryption, and what requires
777 that's outside of the LUKS encryption/verity verification, and we probably
1626 * systemd-repart: read LUKS encryption key from $CREDENTIALS_DIRECTORY
DNEWS467 Changes in disk encryption:
475 * When unlocking devices via TPM, TPM2 parameter encryption is now
477 cannot be eavesdropped to acquire disk encryption keys.
481 use when binding encryption to FIDO2 tokens.
521 credentials that are using an empty encryption key. While this
606 non-interactive symmetric encryption and authentication, based on a
1791 configuring whether the encryption password prompt shall echo the
2124 request synchronous processing of encryption/decryption IO.
3605 LUKS backend, in order to avoid double encryption. The default
3847 used to securely manage home directories with built-in encryption.
[all …]