diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2016-07-01 22:00:52 +0200 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2016-07-01 22:00:52 +0200 |
| commit | 08fcf9628806af202e555bd02b3611e4e9a3d757 (patch) | |
| tree | c2f6705c09debc414580bd118f094522914770a7 /doc | |
| parent | a5f9b45e4a67246f7af2c6fc62de9c531cd314a4 (diff) | |
warn if apt-key is used in scripts/its output parsed
apt-key needs gnupg for most of its operations, but depending on it
isn't very efficient as apt-key is hardly used by users – and scripts
shouldn't use it to begin with as it is just a silly wrapper. To draw
more attention on the fact that e.g. 'apt-key add' should not be used in
favor of "just" dropping a keyring file into the trusted.gpg.d
directory this commit implements the display of warnings.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/apt-key.8.xml | 17 |
1 files changed, 16 insertions, 1 deletions
diff --git a/doc/apt-key.8.xml b/doc/apt-key.8.xml index a847060c0..e0d9f5b95 100644 --- a/doc/apt-key.8.xml +++ b/doc/apt-key.8.xml @@ -13,7 +13,7 @@ &apt-email; &apt-product; <!-- The last update date --> - <date>2015-10-15T00:00:00Z</date> + <date>2016-07-01T00:00:00Z</date> </refentryinfo> <refmeta> @@ -36,6 +36,15 @@ by apt to authenticate packages. Packages which have been authenticated using these keys will be considered trusted. </para> + <para> + Note that if usage of <command>apt-key</command> is desired the additional + installation of the GNU Privacy Guard suite (packaged in + <package>gnupg</package>) 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. <command>apt-key</command> will + try to detect such usage and generates warnings on stderr in these cases. + </para> </refsect1> <refsect1><title>Commands</title> @@ -53,6 +62,12 @@ verified to belong to the owner of the repositories they claim to be for otherwise the &apt-secure; infrastructure is completely undermined. </para> + <para> + Instead of using this command a keyring can be placed directly in the + <filename>/etc/apt/trusted.gpg.d/</filename> directory with a descriptive name + (same rules for filename apply as for &apt-conf; files) and "<literal>gpg</literal>" + as file extension. + </para> </listitem> </varlistentry> |