<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/cmdline/apt-key.in, branch 2.9.0</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.9.0</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.9.0'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2024-02-28T17:22:01Z</updated>
<entry>
<title>Implement gpgv --assert-pubkey-algo=&gt;=rsa2048,ed25519,ed448</title>
<updated>2024-02-28T17:22:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-02-28T14:14:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=50e3fee26ae843a812b1c9ec8531946931773fd3'/>
<id>urn:sha1:50e3fee26ae843a812b1c9ec8531946931773fd3</id>
<content type='text'>
The assertion can be overriden using apt::key::assert-pubkey-algo,
the default is the most opinionated one.

This will inform the user during apt-cdrom add as we do not
pass --quiet to user, so adjust test case.

Add a simple test case for it to test-method-gpgv.

LP: #2055193
</content>
</entry>
<entry>
<title>apt-key: remove carriage returns from armored keyrings before dearmoring</title>
<updated>2023-11-29T20:07:59Z</updated>
<author>
<name>Kenyon Ralph</name>
<email>kenyon@kenyonralph.com</email>
</author>
<published>2023-11-29T20:04:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=18e4c6108e1957a886c1df5054cff73d35a62006'/>
<id>urn:sha1:18e4c6108e1957a886c1df5054cff73d35a62006</id>
<content type='text'>
Without this, the awk script returns nothing if the armored keyring
uses Windows/DOS-style CRLF line endings (since awk is designed for
processing Unix text files). This would result in a NO_PUBKEY error
during the signature verification part of an apt-get update.
</content>
</entry>
<entry>
<title>Warn if the legacy trusted.gpg keyring is used for verification</title>
<updated>2022-02-22T17:25:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2022-01-07T11:43:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=56adf743b02b80a9acc9a2e480bfd15acb94f755'/>
<id>urn:sha1:56adf743b02b80a9acc9a2e480bfd15acb94f755</id>
<content type='text'>
With apt-key going away, people need to manage key files, rather
than keys, so they need to know if any keys are in the legacy keyring.
</content>
</entry>
<entry>
<title>Use short options for cmp</title>
<updated>2021-11-26T14:33:06Z</updated>
<author>
<name>Walter Lozano</name>
<email>walter.lozano@collabora.com</email>
</author>
<published>2021-11-26T14:33:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e7511e1955c250e3e59b2a32b0c29374816b47dd'/>
<id>urn:sha1:e7511e1955c250e3e59b2a32b0c29374816b47dd</id>
<content type='text'>
In order to be consistent with other uses of cmp and to improve compatiblity
with other implementations, like busybox one, change long options to short
ones.

Signed-off-by: Walter Lozano &lt;walter.lozano@collabora.com&gt;
</content>
</entry>
<entry>
<title>Use `command -v` instead of `which`</title>
<updated>2021-11-03T22:02:41Z</updated>
<author>
<name>Ville Skyttä</name>
<email>ville.skytta@iki.fi</email>
</author>
<published>2021-11-03T22:02:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=48d4b06013ae3d80b95cf72efaf9a5e7468de965'/>
<id>urn:sha1:48d4b06013ae3d80b95cf72efaf9a5e7468de965</id>
<content type='text'>
`which` has been deprecated in debianutils 5.0+. The recommended
replacement, `command -v`, is mandated by Debian policy these days, in
addition to being required by POSIX and its predecessor specs at least
since 1994.

Not found commands cause no output from `command -v` per POSIX, so
remove the redundant 2&gt;&amp;1's while at it.
</content>
</entry>
<entry>
<title>apt-key: Allow depending on gpg instead of gnupg</title>
<updated>2020-05-06T10:52:57Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-05-06T10:52:57Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f9f0ae2bbb2d0bfeccddecbf8b9ec07ccd54cd9a'/>
<id>urn:sha1:f9f0ae2bbb2d0bfeccddecbf8b9ec07ccd54cd9a</id>
<content type='text'>
Maintainer scripts that need to use apt-key del might as well
depend on gpg, they don't need the full gnupg suite.
</content>
</entry>
<entry>
<title>Fully deprecate apt-key, schedule removal for Q2/2022</title>
<updated>2020-05-06T10:33:39Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-05-06T10:33:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ee284d5917d09649b68ff1632d44e892f290c52f'/>
<id>urn:sha1:ee284d5917d09649b68ff1632d44e892f290c52f</id>
<content type='text'>
People are still using apt-key add and friends, despite that not
being guaranteed to work. Let's tell them to stop doing so.

We might still want a list command at a future point, but this
needs deciding, and a blanket ban atm seems like a sensible step
until we figured that out.
</content>
</entry>
<entry>
<title>Support multiple keyrings in sources.list Signed-By</title>
<updated>2018-09-11T11:16:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-08-17T14:33:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8375d5b58038fc026098dcccc3de87cd9d740334'/>
<id>urn:sha1:8375d5b58038fc026098dcccc3de87cd9d740334</id>
<content type='text'>
A user can specify multiple fingerprints for a while now, so its seems
counter-intuitive to support only one keyring, especially if this isn't
really checked or enforced and while unlikely mixtures of both should
work properly, too, instead of a kinda random behaviour.
</content>
</entry>
<entry>
<title>apt-key: Pass all instead of gpg-agent to gpgconf --kill</title>
<updated>2018-05-29T15:57:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-05-29T15:57:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=819426013c6ca6310bb469440702b6295dba4498'/>
<id>urn:sha1:819426013c6ca6310bb469440702b6295dba4498</id>
<content type='text'>
We want to kill everything using our temporary directory.

LP: #1773992
</content>
</entry>
<entry>
<title>Fix various typos reported by spellcheckers</title>
<updated>2018-05-04T22:34:27Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-05-04T17:56:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b12bdeaf8acd050c5526ecc05526db70df5fd485'/>
<id>urn:sha1:b12bdeaf8acd050c5526ecc05526db70df5fd485</id>
<content type='text'>
Reported-By: codespell &amp; spellintian
Gbp-Dch: Ignore
</content>
</entry>
</feed>
