X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/bf6d5b428e247dd28fb593cc3677da4e5eee0a54..eee8ee176a5ae3377cc601eb68cdb576b8076761:/doc/apt-key.8.xml?ds=sidebyside diff --git a/doc/apt-key.8.xml b/doc/apt-key.8.xml index 981fa208c..b5319efa3 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; + + 2015-10-15T00:00:00Z + + apt-key 8 + APT @@ -21,14 +28,7 @@ APT key management utility - - - - apt-key - command/ - - - + &synopsis-command-apt-key; Description @@ -40,19 +40,23 @@ 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. - - del keyid + @@ -63,18 +67,18 @@ - export keyid + - Output the key keyid to standard output. + Output the key &synopsis-param-keyid; to standard output. - exportall + @@ -85,7 +89,7 @@ - list + @@ -95,14 +99,57 @@ + + + + - update + List fingerprints of trusted keys. + + + + + + + + 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. + - Update the local keyring with the keyring of Debian archive - keys and removes from the keyring the archive keys which are no - longer valid. + + + + + + + + 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;. + + + + + + + + + + + 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. + + This requires an installed &wget; and an APT build configured to have + a server to fetch from and a master keyring to validate. + + APT in Debian does not support this command, relying on + update instead, but Ubuntu's APT does. @@ -111,26 +158,37 @@ + 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 - /etc/apt/trusted.gpg - Keyring of local trusted keys, new keys will be added here. - + + &file-trustedgpg; /etc/apt/trustdb.gpg Local trust database of archive keys. - /usr/share/keyrings/debian-archive-keyring.gpg - Keyring of Debian archive trusted keys. + &keyring-filename; + Keyring of &keyring-distro; archive trusted keys. - /usr/share/keyrings/debian-archive-removed-keys.gpg - Keyring of Debian archive removed trusted keys. + &keyring-removed-filename; + Keyring of &keyring-distro; archive removed trusted keys. - -