On 10/8/20 2:24 PM, Björn Persson wrote:
Michael Catanzaro wrote:
On Thu, Oct 8, 2020 at 1:28 pm, Paul Wouters <p...@nohats.ca> wrote:
I agree for two reasons. One, the FESCO decision to postpone making
systemd-resolvd the default resolver. I would like to ensure this
change happens properly and securely for f34.
Well it's too late, since we are now in final freeze. FESCo reaffirmed
the systemd-resolved change just last week, so it's clearly not going
to be postponed. I agree that this DNSSEC problem with systemd-resolved
is unfortunate, and I'm sure the systemd developers would appreciate
help fixing it. Anyway, the best time to deal with this would have been
six months ago, when the change was proposed....
The DNSsec problem was brought up by Florian Weimer and Tom Hughes six
months ago, when the change was proposed. Fesco or the change owners
could have chosen to "deal with" the problem then, if they cared about
DNSsec. You Michael replied to Florian and called DNSsec-aware clients
"a quite specialized use-case", so you can't claim that you were unaware
of the issue. "It's too late" rings hollow coming from someone who had
the chance to do something when it wasn't too late.
Björn Persson
Or how about we stick to the Friends Foundation and not make it personal?
--
Erich Eickmeyer
Maintainer
Fedora Jam
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
