<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-releasefile-verification, branch 2.9.17</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.9.17</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.9.17'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2024-12-04T09:14:44Z</updated>
<entry>
<title>gpgv: Merge all keyrings into a single one again</title>
<updated>2024-12-04T09:14:44Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-12-04T08:56:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=48e5af8b5df391e62657b604b2b54885f7ce1c02'/>
<id>urn:sha1:48e5af8b5df391e62657b604b2b54885f7ce1c02</id>
<content type='text'>
gpgv is quite picky, it takes at most 40 keyrings but it also doesn't
even take keyrings with : in the name, generating an ERROR message
instead.

So instead let's always merge the configured keyrings for the source
into a single one.

While we are at it, since we are merging now, let's also add some
rudimentary error checking to what we write into the merged keyring:
If copying into it fails, we should abort.

Reported-by: SuShY on IRC
</content>
</entry>
<entry>
<title>test: Ensure we test both gpgv-g10code and gpgv-sq</title>
<updated>2024-11-22T15:44:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-11-22T15:20:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e983d98c4fcd952ffcbc010b185455913c8af650'/>
<id>urn:sha1:e983d98c4fcd952ffcbc010b185455913c8af650</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test-releasefile-verification: Test empty/invalid signatures</title>
<updated>2024-11-22T15:44:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-11-21T19:01:57Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d2e34a441bad904798bf62fb850d4fb5b1b90656'/>
<id>urn:sha1:d2e34a441bad904798bf62fb850d4fb5b1b90656</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Accept BADSIG instead of EXPSIG for expired signatures</title>
<updated>2024-11-22T15:20:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-11-21T17:51:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=222301d7a36a09db80a8832cd16db41f7946a9ea'/>
<id>urn:sha1:222301d7a36a09db80a8832cd16db41f7946a9ea</id>
<content type='text'>
Sequioa emits KEYEXPIRED + BADSIG instead of EXPSIG + VALIDSIG
</content>
</entry>
<entry>
<title>test-releasefile-verification: Fix signature time</title>
<updated>2024-11-22T15:20:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-11-21T17:49:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=27012a496a9da78f26e9e412a7118dbe00e5c1ec'/>
<id>urn:sha1:27012a496a9da78f26e9e412a7118dbe00e5c1ec</id>
<content type='text'>
The key was only generated in 2010 and only bound in 2016,
so we cannot have signatures from before then, so update
the key accordingly, and change the default expiry to 2017.
</content>
</entry>
<entry>
<title>Rename 'weak digest algorithm' to 'weak algorithm'</title>
<updated>2024-02-28T17:22:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-02-28T15:52:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8a14c18c5b487139948dcb22abd37bffdd9cf5f4'/>
<id>urn:sha1:8a14c18c5b487139948dcb22abd37bffdd9cf5f4</id>
<content type='text'>
This allows us to render public key algorithms as weak as well.
</content>
</entry>
<entry>
<title>Give our test packages proper size information</title>
<updated>2021-06-10T14:38:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2021-06-10T14:38:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=18140e1db1c386a8c6da004956ae8a96152de4d1'/>
<id>urn:sha1:18140e1db1c386a8c6da004956ae8a96152de4d1</id>
<content type='text'>
Temporary hacks should be temporary, especially if they hide bugs. After
fixing one in the previous commit this is just busy work to add download
information to the places which check that output.

Gbp-Dch: Ignore
</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>Support subkeys properly in Signed-By options</title>
<updated>2018-09-11T11:16:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-08-17T09:59:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ff8fa4ab4b80384a9240f0df63181f71077a8d83'/>
<id>urn:sha1:ff8fa4ab4b80384a9240f0df63181f71077a8d83</id>
<content type='text'>
If we limit a file to be signed by a certain key it should usually
accept also being signed by any of this keys subkeys instead of
requiring each subkey to be listed explicitly. If the later is really
wanted we support now also the same syntax as gpg does with appending an
exclamation mark at the end of the fingerprint to force no mapping.
</content>
</entry>
<entry>
<title>fix various typos reported by spellintian</title>
<updated>2017-01-19T14:59:38Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-01-19T14:14:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=93cff633a830e222693fc0f3d78e6e534d1126ee'/>
<id>urn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee</id>
<content type='text'>
Most of them in (old) code comments. The two instances of user visible
string changes the po files of the manpages are fixed up as well.

Gbp-Dch: Ignore
Reported-By: spellintian
</content>
</entry>
</feed>
