New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported DNSSEC algorithms should be considered INSECURE, not BOGUS #19824
Labels
bug 🐛
Programming errors, that need preferential fixing
dnssec
downstream/rhel
Tracking bugs for RHEL
resolve
Milestone
Comments
|
Totally agree. Returning a SERVFAIL is wrong and is leading to an increasing amount of troubles (i.e. it is impossible to enable DNSSEC-validation in this way). https://datatracker.ietf.org/doc/html/rfc6840#section-5.2 |
jacekmigacz
added a commit
to jacekmigacz/systemd
that referenced
this issue
Sep 21, 2022
bluca
pushed a commit
to jacekmigacz/systemd
that referenced
this issue
Sep 30, 2022
bluca
pushed a commit
that referenced
this issue
Sep 30, 2022
bluca
pushed a commit
to bluca/systemd
that referenced
this issue
Jan 27, 2023
…OGUS Resolves: systemd#19824 (cherry picked from commit 1ca3600) (cherry picked from commit e91ea65)
valentindavid
pushed a commit
to valentindavid/systemd
that referenced
this issue
Aug 8, 2023
…OGUS Resolves: systemd#19824 (cherry picked from commit 1ca3600)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug 🐛
Programming errors, that need preferential fixing
dnssec
downstream/rhel
Tracking bugs for RHEL
resolve
systemd version the issue has been seen with
Used distribution
Linux kernel version used (
uname -a)CPU architecture issue was seen on
Expected behaviour you didn't see
Unexpected behaviour you saw
Steps to reproduce the problem
Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: