Bug 2325406 - systemd-resolved: DNSSEC unsupported algorithms are failing instead of insecure
Summary: systemd-resolved: DNSSEC unsupported algorithms are failing instead of insecure
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 41
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/systemd/systemd/is...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-12 08:53 UTC by Petr Menšík
Modified: 2025-12-16 17:32 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 17:32:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd issues 35112 0 None open F41 systemd-resolved fails to resolve domains with DNSSEC algo 5 and 7 with DEFAULT crypto policy 2024-11-12 08:54:22 UTC
Github systemd systemd issues 35126 0 None open resolved: DNSSEC unknown algorithms are failing instead of insecure 2024-11-12 08:54:22 UTC

Description Petr Menšík 2024-11-12 08:53:54 UTC
DNSSEC unsupported algorithms are failing instead of insecure, including SHA-1 algorithms deactivated by crypto-policy in Fedora 41.

Reproducible: Always

Steps to Reproduce:
1. set DNSSEC=yes in /etc/systemd/resolved
2. systemctl restart systemd-resolved
3. xdg-open https://rootcanary.org/test.html
Actual Results:  
Unsupported algorithms are failing, instead of reporting just insecure response. That is not how it should behave.

Expected Results:  
Only green and yellow icons appear for all algorithms. There should not be any red.

Reported at upstream: https://github.com/systemd/systemd/issues/35126

But I think this should be fixed in already released Fedora 41 too, not only in more recent versions. If it behaves the same way on F40, should be fixed there too.

Is there time already to write into systemd documentation, that its DNSSEC support is considered experimental and not for a production use?

Comment 1 Petr Menšík 2024-11-12 08:56:42 UTC
Does it work the same way also in RHEL9+, where SHA1 has been disabled for longer time?

Comment 2 Petr Menšík 2024-11-12 09:58:41 UTC
Marking as regression. There are some yellow in systemd-resolved-255.13-1.fc40.x86_64. While it still contains red color, it is not full of it.

Tested in live iso system, systemd-resolved fully upgraded.

Comment 3 Adam Williamson 2025-12-02 01:35:04 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Samyak Jain (RedHat) 2025-12-16 17:32:20 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.