Hello Julian, or anyone else affected, Accepted apt into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.8.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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.0: Promote weak key warnings to errors Status in apt package in Ubuntu: Fix Released Status in apt source package in Noble: Fix Committed Bug description: ⚠️ 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, safe 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. Additional tests are: 1. (promotion to error) Take a repository that has a weak RSA key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. We don't have any tests for the test changes or the documentation translation URL unfuzzying. [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
