Debian Codegraph @

upstream/debian-trixie/man1/systemd-keyutil.1

raw
1 '\" t
2 .TH "SYSTEMD\-KEYUTIL" "1" "" "systemd 257.13" "systemd-keyutil"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd-keyutil \- Perform various operations on private keys and X\&.509 certificates
24 .SH "SYNOPSIS"
25 .HP \w'\fBsystemd\-keyutil\fR\ 'u
26 \fBsystemd\-keyutil\fR [OPTIONS...] {COMMAND}
27 .SH "DESCRIPTION"
28 .PP
29 \fBsystemd\-keyutil\fR
30 can be used to perform various operations on private keys and X\&.509 certificates\&.
31 .SH "COMMANDS"
32 .PP
33 \fBvalidate\fR
34 .RS 4
35 Checks that we can load the private key and certificate specified with
36 \fB\-\-private\-key=\fR
37 and
38 \fB\-\-certificate=\fR
39 respectively\&.
40 .sp
41 As a side effect, if the private key is loaded from a PIN\-protected hardware token, this command can be used to cache the PIN in the kernel keyring\&. The
42 \fI$SYSTEMD_ASK_PASSWORD_KEYRING_TIMEOUT_SEC\fR
43 and
44 \fI$SYSTEMD_ASK_PASSWORD_KEYRING_TYPE\fR
45 environment variables can be used to control how long and in which kernel keyring the PIN is cached\&.
46 .sp
47 Added in version 257\&.
48 .RE
49 .PP
50 \fBpublic\fR
51 .RS 4
52 This commands prints the public key in PEM format extracted from either the certificate given with
53 \fB\-\-certificate=\fR
54 or the private key given with
55 \fB\-\-private\-key=\fR\&.
56 .sp
57 Added in version 257\&.
58 .RE
59 .SH "OPTIONS"
60 .PP
61 The following options are understood:
62 .PP
63 \fB\-\-private\-key=\fR\fB\fIPATH/URI\fR\fR, \fB\-\-private\-key\-source=\fR\fB\fITYPE\fR\fR\fB[:\fR\fB\fINAME\fR\fR\fB]\fR, \fB\-\-certificate=\fR\fB\fIPATH\fR\fR, \fB\-\-certificate\-source=\fR\fB\fITYPE\fR\fR\fB[:\fR\fB\fINAME\fR\fR\fB]\fR
64 .RS 4
65 Set the private key and certificate to use\&. The
66 \fB\-\-certificate=\fR
67 option takes a path to a PEM encoded X\&.509 certificate or a URI that\*(Aqs passed to the OpenSSL provider configured with
68 \fB\-\-certificate\-source\fR\&. The
69 \fB\-\-certificate\-source\fR
70 takes one of
71 "file"
72 or
73 "provider", with the latter being followed by a specific provider identifier, separated with a colon, e\&.g\&.
74 "provider:pkcs11"\&. The
75 \fB\-\-private\-key=\fR
76 option can take a path or a URI that will be passed to the OpenSSL engine or provider, as specified by
77 \fB\-\-private\-key\-source=\fR
78 as a
79 "type:name"
80 tuple, such as
81 "engine:pkcs11"\&.
82 .sp
83 Added in version 257\&.
84 .RE
85 .PP
86 \fB\-h\fR, \fB\-\-help\fR
87 .RS 4
88 Print a short help text and exit\&.
89 .RE
90 .PP
91 \fB\-\-version\fR
92 .RS 4
93 Print a short version string and exit\&.
94 .RE
95 .SH "SEE ALSO"
96 .PP
97 \fBsystemd-sbsign\fR(1), \fBsystemd-measure\fR(1)