<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-apt-key-used-in-maintainerscript, branch 1.3_pre2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_pre2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_pre2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-07-01T20:00:52Z</updated>
<entry>
<title>warn if apt-key is used in scripts/its output parsed</title>
<updated>2016-07-01T20:00:52Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-01T20:00:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=08fcf9628806af202e555bd02b3611e4e9a3d757'/>
<id>urn:sha1:08fcf9628806af202e555bd02b3611e4e9a3d757</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>warn if apt-key is run unconditionally in maintainerscript</title>
<updated>2016-05-01T13:50:04Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-01T12:43:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5f17b19f8f99eb6f80a10846d5891f53c16178dc'/>
<id>urn:sha1:5f17b19f8f99eb6f80a10846d5891f53c16178dc</id>
<content type='text'>
We want to stop hard-depending on gnupg and for this it is essential
that apt-key isn't used in any critical execution path, which
maintainerscript are. Especially as it is likely that these script call
apt-key either only for (potentially now outdated cleanup) or still not
use the much simpler trusted.gpg.d infrastructure.
</content>
</entry>
</feed>
