This bug was fixed in the package apt - 2.8.3
---------------
apt (2.8.3) noble; urgency=medium
* Revert increased key size requirements from 2.8.0-2.8.2 (LP: #2073126)
- Revert "Only install 00-temporary-rsa1024 for >=2.7.6 and improve comment"
- Revert "Only warn about <rsa2048 when upgrading from 2.7.x to 2.8.x"
- Revert rsa1024 to warnings again
This leaves the mechanisms in place and no longer warns about NIST curves.
* Fix keeping back removals of obsolete packages; and return an error if
ResolveByKeep() is unsuccessful (LP: #2078720)
* Fix buffer overflow, stack overflow, exponential complexity in
apt-ftparchive Contents generation (LP: #2083697)
- ftparchive: Mystrdup: Add safety check and bump buffer size
- ftparchive: contents: Avoid exponential complexity and overflows
- test framework: Improve valgrind support
- test: Check that apt-ftparchive handles deep paths
- Workaround valgrind "invalid read" in ExtractTar::Go by moving large
buffer from stack to heap. The large buffer triggered some bugs in
valgrind stack clash protection handling.
apt (2.8.2) noble; urgency=medium
* Only install 00-temporary-rsa1024 for >=2.7.6 and improve comment
(follow-up for LP: #2073126)
apt (2.8.1) noble; urgency=medium
* Only revoke weak RSA keys for now, add 'next' and 'future' levels
(backported from 2.9.7)
Note that the changes to warn about keys not matching the future level
in the --audit level are not fully included, as the --audit feature
has not yet been backported. (LP: #2073126)
* Introduce further mitigation on upgrades from 2.7.x to allow these
systems to continue using rsa1024 repositories with warnings
until the 24.04.2 point release (LP: #2073126)
apt (2.8.0) noble; urgency=medium
[ Julian Andres Klode ]
* Revert "Temporarily downgrade key assertions to "soon worthless""
We temporarily downgraded the errors to warnings to give the
launchpad PPAs time to be fixed, but warnings are not safe:
Untrusted keys could be hiding on your system, but just not
used at the moment. Hence revert this so we get the errors we
want. (LP: #2060721)
* Branch off the stable 2.8.y branch for noble:
- CI: Test in ubuntu:noble images for 2.8.y
- debian/gbp.conf: Point at the 2.8.y branch
[ David Kalnischkies ]
* Test suite fixes:
- Avoid subshell hiding failure report from testfilestats
- Ignore umask of leftover diff_Index in failed pdiff test
* Documentation translation fixes:
- Fix and unfuzzy previous VCG/Graphviz URI change
-- Julian Andres Klode <juli...@ubuntu.com> Tue, 22 Oct 2024 15:02:22
+0200
** Changed in: apt (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2060721
Title:
APT 2.8.4+: Promote weak key warnings to errors
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Noble:
Fix Released
Bug description:
(2.8.3 update references this bug as previous uploads tried to fix it
and have not been fully reverted, per discussion with rbasak we agreed
to just ignore this bug for SRU verification; as in mark it
verification-done, and then re-open the bug after the package migrated
For the discussion, see
https://irclogs.ubuntu.com/2024/10/16/%23ubuntu-devel.html
)
⚠️ Only land this in the release/updates pocket after PPAs have been
resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development series for 2.8, and this is
the only change left for the 2.8 release, save for some minor
translation/test suite improvements)
(Please also look at bug 2073126 for the follow-up changes to mitigate
regression potential).
[Impact]
APT is currently just warning about keys that it should be rejecting to give
Launchpad time to resign PPAs. This needs to be bumped to an error such that
the crypto policy is fully implemented and we only trust keys that are still
being trusted. #2055193
A warning provides some help right now to third-parties to fix their
repositories, but it's not *safe*: A repository could have multiple
signing keys and be signed by a good key now, then later, a previous
key still in trusted.gpg.d could be revoked and we'd degrade to
warnings, which, given that we update in the background automatically,
the user may not see.
Other fixes:
- The test suite has been made less flaky in two places
- Documentation translation has been unfuzzied for URL changes in 2.7.14
[Test plan]
The vast regression test suite prevents regression in other components.
Test Case A: Existing noble system (warning)
0. Update an existing noble container to the new APT
1. Observe/etc/apt/apt.conf.d/00-temporary-rsa1024 being created
2. Add a PPA with an old 1024-bit signing key
3. Run apt update
4. Observe that the PPA is updated with a warning
Test Case B: New noble system (error)
0. Bootstrap a new noble system including apt from proposed (using e.g.
mmdebstrap)
1. Observe NO /etc/apt/apt.conf.d/00-temporary-rsa1024
2. Add a PPA with an old 1024-bit signing key
3. Run apt update
4. Observe that the PPA is not updated, but the other repositories are
Test Case C: mantic -> noble (error)
0. Upgrade mantic to noble w/ apt from proposed, observe behavior as
in B
Test Case D: jammy -> noble (error)
0. Upgrade jammy to noble w/ apt from proposed, observe behavior as in
B
[Where problems could occur]
apt will start to fail updates of repositories with weak signing keys, but it
will have warned users about that before. Given that it is still early in the
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the
right tradeoff for future security.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
