This bug was fixed in the package dns-root-data -
2024071801~ubuntu0.22.04.1
---
dns-root-data (2024071801~ubuntu0.22.04.1) jammy; urgency=medium
* Backport data update to include DNSSEC root trust anchor of KSK-2024
(LP: #2086795)
dns-root-data (2024071801) unstable; urgency=m
This bug was fixed in the package dns-root-data -
2024071801~ubuntu0.20.04.1
---
dns-root-data (2024071801~ubuntu0.20.04.1) focal; urgency=medium
* Backport data update to include DNSSEC root trust anchor of KSK-2024
(LP: #2086795)
- d/control: downgrade to debhelper-compat
This bug was fixed in the package dns-root-data -
2024071801~ubuntu0.24.04.1
---
dns-root-data (2024071801~ubuntu0.24.04.1) noble; urgency=medium
* Backport data update to include DNSSEC root trust anchor of KSK-2024
(LP: #2086795)
dns-root-data (2024071801) unstable; urgency=m
Wow, it seems verifying all releases and doing updates in multiple browser tabs
made it re-add the -needed for those releases done in the other tab.
Silly, but lessons learned - updating tags ...
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-noble
** Ta
This bug was fixed in the package dns-root-data -
2024071801~ubuntu0.24.10.1
---
dns-root-data (2024071801~ubuntu0.24.10.1) oracular; urgency=medium
* Backport data update to include DNSSEC root trust anchor of KSK-2024
(LP: #2086795)
dns-root-data (2024071801) unstable; urgenc
Since this was more a formal than a functional check it was a bit
verbose, but all we defined worked as expected and therefore all
verification tags are set to done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Noble verification:
root@n-sru:~# apt policy dns-root-data
dns-root-data:
Installed: 2023112702~willsync1
Candidate: 2023112702~willsync1
Version table:
2024071801~ubuntu0.24.04.1 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
*** 2023112702~willsyn
Rechecked official keys of the day, matching:
openssl smime -verify -CAfile icannbundle.pem -inform der -in root-anchors.p7s
-content root-anchors.xml
http://data.iana.org/root-anchors/root-anchors.xml";>
.
19036
8
2
49AAC11D7B6F6446702E54A1607371607A1A4
Oracular verification:
root@o-sru:~# apt policy dns-root-data
dns-root-data:
Installed: 2024041801
Candidate: 2024041801
Version table:
2024071801~ubuntu0.24.10.1 100
100 http://archive.ubuntu.com/ubuntu oracular-proposed/main amd64
Packages
*** 2024041801 500
500 http
Focal verification:
root@f-sru:~# apt policy dns-root-data
dns-root-data:
Installed: 2023112702~ubuntu0.20.04.1
Candidate: 2024071801~ubuntu0.20.04.1
Version table:
2024071801~ubuntu0.20.04.1 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
*** 202311
Jammy verification:
root@j-sru:~# apt policy dns-root-data
dns-root-data:
Installed: 2023112702~ubuntu0.22.04.1
Candidate: 2024071801~ubuntu0.22.04.1
Version table:
2024071801~ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
*** 202311
FYI The test fail was an infrastructure issue and resolved in
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/ppc64el/b/bind9/20250210_090643_8f8e5@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Hello Matt, or anyone else affected,
Accepted dns-root-data into oracular-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/dns-root-
data/2024071801~ubuntu0.24.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this ne
** Changed in: dns-root-data (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: dns-root-data (Ubuntu Noble)
Status: Fix Committed => In Progress
** Changed in: dns-root-data (Ubuntu Jammy)
Status: Fix Committed => In Progress
--
You received this bug notifi
The removal of root.hints.sig might need to be discussed in the context
of the backports.
I think it isn't needed and it allows easier cross release usage and
maintenance with the content being the same. But that is for the SRU
team to decide.
I added it to regression considerations to force awar
Seeing them in -unapproved, updating state
** Changed in: dns-root-data (Ubuntu Focal)
Status: Triaged => Fix Committed
** Changed in: dns-root-data (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Changed in: dns-root-data (Ubuntu Noble)
Status: Triaged => Fix Committed
I was able to come up with steps to verify the build result as delivered by the
package as well as adding a simple test with named to ensure it is not breaking
by e.g. the key being in the future.
Thereby the associated MRs that are up for review now before upload into the
Ubuntu SRU queue.
**
** Description changed:
[ Impact ]
* ICANN has generated the next DNSSEC root trust anchor, KSK-2024.
* ICANN's current plan is that it will be required around 2026-10-11
to 2027-01-11, but the sooner it's updated, the more unmaintained
installations will have it when the t
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/dns-root-data/+git/dns-root-data/+merge/476934
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/dns-root-data/+git/dns-root-data/+merge/476935
** Merge proposal linked:
https://cod
** Description changed:
[ Impact ]
* ICANN has generated the next DNSSEC root trust anchor, KSK-2024.
* ICANN's current plan is that it will be required around 2026-10-11
to 2027-01-11, but the sooner it's updated, the more unmaintained
installations will have it when the t
** Description changed:
[ Impact ]
- * ICANN has generated the next DNSSEC root trust anchor, KSK-2024.
+ * ICANN has generated the next DNSSEC root trust anchor, KSK-2024.
- * ICANN's current plan is that it will be required around 2026-10-11
-to 2027-01-11, but the sooner it's upd
** Also affects: dns-root-data (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: dns-root-data (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: dns-root-data (Ubuntu Plucky)
Importance: Undecided
Assignee: Christian Ehrhardt (paelzer)
Debian has done the update really well also updating the parsing and handling
and the documentation.
I think I'll go for backporting the whole instead of just the data, that should
be better.
** Description changed:
+ [ Impact ]
+
+ * ICANN has generated the next DNSSEC root trust anchor, KSK
** Changed in: dns-root-data (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086795
Title:
New DNSSEC root trust anchor
To mana
** Changed in: dns-root-data (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086795
Title:
New DNSSEC root trust anchor
To manage notifications
Hi Matt,
It looks like dns-root-data should automatically sync this into plucky
from Debian once the fix is available in sid, but am guessing you feel
it'll need SRUs to all supported releases? Looks like we've needed to
do roll out updates for this package in the past (LP: #2045297)
Patch neede
** Changed in: dns-root-data (Debian)
Status: Unknown => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086795
Title:
New DNSSEC root trust anchor
To manage notifications about
27 matches
Mail list logo
