1APT-KEY(8)                            APT                           APT-KEY(8)
2
3
4

NAME

6       apt-key - APT key management utility
7

SYNOPSIS

9       apt-key [--keyring filename] {add filename | del keyid | export keyid |
10               exportall | list | finger | adv | update | net-update |
11               {-v | --version} | {-h | --help}}
12

DESCRIPTION

14       apt-key is used to manage the list of keys used by apt to authenticate
15       packages. Packages which have been authenticated using these keys will
16       be considered trusted.
17
18       Note that if usage of apt-key is desired the additional installation of
19       the GNU Privacy Guard suite (packaged in gnupg) is required. For this
20       reason alone the programmatic usage (especially in package maintainer
21       scripts!) is strongly discouraged. Further more the output format of
22       all commands is undefined and can and does change whenever the
23       underlying commands change.  apt-key will try to detect such usage and
24       generates warnings on stderr in these cases.
25

SUPPORTED KEYRING FILES

27       apt-key supports only the binary OpenPGP format (also known as "GPG key
28       public ring") in files with the "gpg" extension, not the keybox
29       database format introduced in newer gpg(1) versions as default for
30       keyring files. Binary keyring files intended to be used with any apt
31       version should therefore always be created with gpg --export.
32
33       Alternatively, if all systems which should be using the created keyring
34       have at least apt version >= 1.4 installed, you can use the ASCII
35       armored format with the "asc" extension instead which can be created
36       with gpg --armor --export.
37

COMMANDS

39       add filename
40           Add a new key to the list of trusted keys. The key is read from the
41           filename given with the parameter filename or if the filename is -
42           from standard input.
43
44           It is critical that keys added manually via apt-key are verified to
45           belong to the owner of the repositories they claim to be for
46           otherwise the apt-secure(8) infrastructure is completely
47           undermined.
48
49           Note: Instead of using this command a keyring should be placed
50           directly in the /etc/apt/trusted.gpg.d/ directory with a
51           descriptive name and either "gpg" or "asc" as file extension.
52
53       del keyid
54           Remove a key from the list of trusted keys.
55
56       export keyid
57           Output the key keyid to standard output.
58
59       exportall
60           Output all trusted keys to standard output.
61
62       list, finger
63           List trusted keys with fingerprints.
64
65       adv
66           Pass advanced options to gpg. With adv --recv-key you can e.g.
67           download key from keyservers directly into the trusted set of keys.
68           Note that there are no checks performed, so it is easy to
69           completely undermine the apt-secure(8) infrastructure if used
70           without care.
71
72       update (deprecated)
73           Update the local keyring with the archive keyring and remove from
74           the local keyring the archive keys which are no longer valid. The
75           archive keyring is shipped in the archive-keyring package of your
76           distribution, e.g. the debian-archive-keyring package in Debian.
77
78           Note that a distribution does not need to and in fact should not
79           use this command any longer and instead ship keyring files in the
80           /etc/apt/trusted.gpg.d/ directory directly as this avoids a
81           dependency on gnupg and it is easier to manage keys by simply
82           adding and removing files for maintainers and users alike.
83
84       net-update
85           Perform an update working similarly to the update command above,
86           but get the archive keyring from a URI instead and validate it
87           against a master key. This requires an installed wget(1) and an APT
88           build configured to have a server to fetch from and a master
89           keyring to validate. APT in Debian does not support this command,
90           relying on update instead, but Ubuntu's APT does.
91

OPTIONS

93       Note that options need to be defined before the commands described in
94       the previous section.
95
96       --keyring filename
97           With this option it is possible to specify a particular keyring
98           file the command should operate on. The default is that a command
99           is executed on the trusted.gpg file as well as on all parts in the
100           trusted.gpg.d directory, though trusted.gpg is the primary keyring
101           which means that e.g. new keys are added to this one.
102

FILES

104       /etc/apt/trusted.gpg
105           Keyring of local trusted keys, new keys will be added here.
106           Configuration Item: Dir::Etc::Trusted.
107
108       /etc/apt/trusted.gpg.d/
109           File fragments for the trusted keys, additional keyrings can be
110           stored here (by other packages or the administrator). Configuration
111           Item Dir::Etc::TrustedParts.
112

SEE ALSO

114       apt-get(8), apt-secure(8)
115

BUGS

117       APT bug page[1]. If you wish to report a bug in APT, please see
118       /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.
119

AUTHOR

121       APT was written by the APT team <apt@packages.debian.org>.
122

AUTHORS

124       Jason Gunthorpe
125
126       APT team
127

NOTES

129        1. APT bug page
130           http://bugs.debian.org/src:apt
131
132
133
134APT 2.0.2                        04 April 2019                      APT-KEY(8)
Impressum