X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/ac3dee0e5091f19b77de96eec5241cb57c13f2a1..782c60a6bf7dddcc71dbdbc4a0eea85824076fa9:/doc/apt-key.8.xml diff --git a/doc/apt-key.8.xml b/doc/apt-key.8.xml index 981fa208c..093abfe8a 100644 --- a/doc/apt-key.8.xml +++ b/doc/apt-key.8.xml @@ -1,18 +1,25 @@ - -%aptent; - + %aptent; + %aptverbatiment; + %aptvendor; ]> - &apt-docinfo; - + + &apt-author.jgunthorpe; + &apt-author.team; + &apt-email; + &apt-product; + + 2016-07-07T00:00:00Z + + apt-key 8 + APT @@ -21,14 +28,7 @@ APT key management utility - - - - apt-key - command/ - - - + &synopsis-command-apt-key; Description @@ -36,23 +36,42 @@ by apt to authenticate packages. Packages which have been authenticated using these keys will be considered trusted. + + Note that if usage of apt-key is desired the additional + installation of the GNU Privacy Guard suite (packaged in + gnupg) is required. For this reason alone the programatic + usage (especially in package maintainerscripts!) is strongly discouraged. + Further more the output format of all commands is undefined and can and does + change whenever the underlying commands change. apt-key will + try to detect such usage and generates warnings on stderr in these cases. + Commands - add filename + - - Add a new key to the list of trusted keys. The key is read - from filename, or standard input if - filename is -. + Add a new key to the list of trusted keys. + The key is read from the filename given with the parameter + &synopsis-param-filename; or if the filename is - + from standard input. + + + It is critical that keys added manually via apt-key are + verified to belong to the owner of the repositories they claim to be for + otherwise the &apt-secure; infrastructure is completely undermined. + + + Instead of using this command a keyring can be placed directly in the + /etc/apt/trusted.gpg.d/ directory with a descriptive name + (same rules for filename apply as for &apt-conf; files) and "gpg" + as file extension. - - del keyid + @@ -63,18 +82,18 @@ - export keyid + - Output the key keyid to standard output. + Output the key &synopsis-param-keyid; to standard output. - exportall + @@ -85,51 +104,86 @@ - list + , - List trusted keys. + List trusted keys with fingerprints. - update + - - Update the local keyring with the keyring of Debian archive - keys and removes from the keyring the archive keys which are no - longer valid. - + Pass advanced options to gpg. With adv --recv-key you + can e.g. download key from keyservers directly into the the trusted set of + keys. Note that there are no checks performed, so it is + easy to completely undermine the &apt-secure; infrastructure if used without + care. - - - Files - - /etc/apt/trusted.gpg - Keyring of local trusted keys, new keys will be added here. + (deprecated) + + + Update the local keyring with the archive keyring and remove from + the local keyring the archive keys which are no longer valid. + The archive keyring is shipped in the archive-keyring package of your + distribution, e.g. the &keyring-package; package in &keyring-distro;. + + + Note that a distribution does not need to and in fact should not use + this command any longer and instead ship keyring files in the + /etc/apt/trusted.gpg directory directly as this + avoids a dependency on gnupg and it is easier to manage + keys by simply adding and removing files for maintainers and users alike. + + + + + + - /etc/apt/trustdb.gpg - Local trust database of archive keys. - + Perform an update working similarly to the update command above, + but get the archive keyring from a URI instead and validate it against a master key. - /usr/share/keyrings/debian-archive-keyring.gpg - Keyring of Debian archive trusted keys. - + This requires an installed &wget; and an APT build configured to have + a server to fetch from and a master keyring to validate. - /usr/share/keyrings/debian-archive-removed-keys.gpg - Keyring of Debian archive removed trusted keys. + APT in Debian does not support this command, relying on + update instead, but Ubuntu's APT does. + + + + + + + Options +Note that options need to be defined before the commands described in the previous section. + + + With this option it is possible to specify a particular keyring + file the command should operate on. The default is that a command is executed + on the trusted.gpg file as well as on all parts in the + trusted.gpg.d directory, though trusted.gpg + is the primary keyring which means that e.g. new keys are added to this one. + + + + + + Files + + &file-trustedgpg;