summaryrefslogtreecommitdiff
path: root/man/systemd-creds.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-04-21 15:36:03 +0200
committerLuca Boccassi <luca.boccassi@gmail.com>2022-04-21 23:23:14 +0200
commitd43ea6c8ff0b53453e28839f468c932726f2a8c4 (patch)
tree9103526dbf727489e9973c2d2c4a4e952a51b8e1 /man/systemd-creds.xml
parent92c9f47d05548c14646c257cfdc4959f0b82a9bd (diff)
downloadsystemd-d43ea6c8ff0b53453e28839f468c932726f2a8c4.tar.gz
man: make clear that encrypted credentials are also authenticated
We use authenticated encryption, and that deserves mention. This in particular relevant as the fact they are authenticated makes the credentials useful as initrd parameterization items.
Diffstat (limited to 'man/systemd-creds.xml')
-rw-r--r--man/systemd-creds.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/man/systemd-creds.xml b/man/systemd-creds.xml
index 342c39a4e2..2427311770 100644
--- a/man/systemd-creds.xml
+++ b/man/systemd-creds.xml
@@ -90,7 +90,7 @@
<term><command>encrypt</command> <replaceable>input|-</replaceable> <replaceable>output|-</replaceable></term>
<listitem><para>Loads the specified (unencrypted plaintext) input credential file, encrypts it and
- writes the (encrypted ciphertext) version to the specified output credential file. The resulting file
+ writes the (encrypted ciphertext) output to the specified target credential file. The resulting file
may be referenced in the <varname>LoadCredentialEncrypted=</varname> setting in unit files, or its
contents used literally in <varname>SetCredentialEncrypted=</varname> settings.</para>
@@ -102,8 +102,8 @@
output path is specified as <literal>-</literal> the credential name cannot be derived from the file
system path, and thus should be specified explicitly via the <option>--name=</option> switch.</para>
- <para>The credential data is encrypted symmetrically with one of the following encryption
- keys:</para>
+ <para>The credential data is encrypted and authenticated symmetrically with one of the following
+ encryption keys:</para>
<orderedlist>
<listitem><para>A secret key automatically derived from the system's TPM2 chip. This encryption key
@@ -145,8 +145,8 @@
<optional><replaceable>output|-</replaceable></optional></term>
<listitem><para>Undoes the effect of the <command>encrypt</command> operation: loads the specified
- (encrypted ciphertext) input credential file, decrypts it and writes the (decrypted plaintext)
- version to the specified output credential file.</para>
+ (encrypted ciphertext) input credential file, decrypts and authenticates it and writes the (decrypted
+ plaintext) output to the specified target credential file.</para>
<para>Takes one or two file system paths. The file name part of the input path is compared with the
credential name embedded in the encrypted file. If it does not match decryption fails. This is done