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 =2.7.6 and impr
Removing block-proposed-noble as update-manager and apt are both ready
to release now, having just verified update-manager/oracular.
** Tags removed: block-proposed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I first upgraded apt, libapt-pkg6.0t64 to 2.8.3.
Validation for RSA1024 remaining weak:
root@noble:~# gpg --quick-gen-key j...@debian.org rsa1024
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
We need to generate a lot of random bytes. It is a good idea to
Already in 2015 the nice folks at https://weakdh.org/ were hypothesizing
that 1024 bit DSA was unsafe against very well resourced attackers.
We have to draw a line somewhere, and we might as well draw it here,
today. Affected parties can modify their APT configuration, right? I'm
fine regressing d
The update inadvertently disabled DSA signatures. We believed DSA
signatures (1) could not use SHA2 hashes and (2) were not trusted
anyway, but it seems that xenial, which is dual-signed with a DSA1024
bit key has a SHA512 DSA1024 signature and that is still considered
trusted.
This is causing the
The level has changed:
Algorithms missing in "APT::Key::Assert-Pubkey-Algo" cause errors now,
whereas algorithms in "APT::Key::Assert-Pubkey-Algo::Next" cause
warnings.
Accordingly, the values were moved around such that
"APT::Key::Assert-Pubkey-Algo::Next" matches the old
APT::Key::Assert-Pubke
Ah, sorry about neglecting the other curves here. I'm much less
concerned about the curve changes.
Someone who chooses these curves has thought about it and made their
choice. Someone who is on RSA1024 might not know that they're on the
"very best of y2k" playlist. The NSA may have suggested every
So to summarize, and please confirm or deny my understanding below,
comparing to 2.7.14build2 which is current noble release+updates:
- Assert-Pubkey-Algo reintroduces >= rsa1024 (was rsa2048), and allows more
nist curves[1]. It's downgrading the RSA key size to 1024.
- there is no error whatsoev
Thanks @Seth! Your comment #18 seems to have focused mostly on the RSA
keys, did you get a chance to also look at the new NIST, brainpoolP, and
secp algorithms that were added/swapped around? From the table in
comment #22 (also comment #20), looks like another change is that NIST
P-{256,384,512} in
Here is a screenshot of the document from comment #20
** Attachment added: "apt-security-levels.png"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2073126/+attachment/5867457/+files/apt-security-levels.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I tested with (only changed rsa from the defaults):
APT::Key::Assert-Pubkey-Algo
">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";
APT::Key::Assert-Pubkey-Algo::Next
">=rsa5120,ed25519,ed448,nistp256,nistp384,nistp512";
Ah, thank you both Andreas and Julian for working with me to understand
these changes better.
If we're already supporting rsa1024 in noble, that would explain why we
haven't seen a deluge of support requests around it. Fair. Tightening it
in an update a year later, absent impressive news, would be
Put the security levels (noble release vs unapproved vs oracular) into a
table in
https://docs.google.com/document/d/1rIREl1ebAoJXyqjig5MlV1-Jae9EREcApuVMlKT1whQ/edit?tab=t.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
> I don't understand why today is the right day to allow weaker RSA
keys.
I don't think that changed. To recap (and these changes are confusing,
yes, but this is my understanding of the final result):
# Noble release
- there is only one list of crypto algorithms: Assert-Pubkey-Algo
- anything NOT
Thanks for your summary, Andreas, I found it very helpful.
This guide appeared to be the newest from NIST that I could find on the
topic of key lengths
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar3.ipd.pdf
-- page 21 (marked 11 on the page) appears to say n=1024 is still
@ubuntu-security, could I please get your take on the changes introduced
by this SRU? I believe I summarized them in comment #16 (unless @juliank
chimes in with a correction!).
It's basically the list of crypto algorithms that need checking.
RSA1024 still triggers a "weak key" warning.
https://
So from my understanding, these are the big changes in this SRU,
regarding the crypto config.
a) Algorithms MISSING from Assert-Pubkey-Algo are now treated as an
ERROR, whereas before (noble release) they were WARNINGS;
b) The list of algorithms in Assert-Pubkey-Algo changed:
">=rsa2048,ed2551
> Algorithms missing in "APT::Key::Assert-Pubkey-Algo" cause errors now,
> whereas algorithms in
> "APT::Key::Assert-Pubkey-Algo::Next" cause warnings.
The word "missing" is, er, missing, in the second part of that sentence,
right? The full correct sentence is (diff capitalized by me):
Algori
** Description changed:
- (This is uploaded to noble as 2.8.1 per
- https://wiki.ubuntu.com/AptUpdates)
+ (Please see https://wiki.ubuntu.com/AptUpdates for the versioning)
[Impact]
- We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about rec
** Changed in: apt (Ubuntu Noble)
Milestone: ubuntu-24.04.1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073126
Title:
More nuanced public key algorithm revocation
To manage notificat
** Description changed:
(This is uploaded to noble as 2.8.1 per
https://wiki.ubuntu.com/AptUpdates)
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning
This bug was fixed in the package apt - 2.9.7
---
apt (2.9.7) unstable; urgency=medium
[ sid ]
* Show installed version (not candidate version) while removing a package
[ David Kalnischkies ]
* Parse snapshot option for apt show/list (Closes: #1075819)
[ Frans Spiesschaert
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073126
Title:
More nuanced public key algorithm revocation
To manage notifications about this bug go to:
https://bugs.
** Tags added: block-proposed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073126
Title:
More nuanced public key algorithm revocation
To manage notifications about this bug go to:
https://b
this upload is not to be accepted to -updates before the discussion on
ubuntu-release@ is concluded
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073126
Title:
More n
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/Tes
** Description changed:
+ (This is uploaded to noble as 2.8.1 per
+ https://wiki.ubuntu.com/AptUpdates)
+
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning
** Description changed:
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.
We also revoked additional ECC curves, which may
** Changed in: apt (Ubuntu Oracular)
Status: New => Fix Committed
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073126
Title:
More nuanced public key algo
** Description changed:
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.
We also revoked additional ECC curves, which may
** Description changed:
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.
+
+ We also revoked additional ECC curves, which may
** Description changed:
- APT 2.9.x and 2.8.0 revoke any of the non-asserted algorithms, we should
- modify the mechanism such that only RSA1024 is raised to an error to
- avoid unwanted regressions while still keeping the set of fully
- supported algorithms small.
+ [Impact]
+ We have received fe
32 matches
Mail list logo
