Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 2, 2022 at 3:28 PM Chris Adams <linux@xxxxxxxxxxx> wrote:
Once upon a time, Florian Weimer <fweimer@xxxxxxxxxx> said:
> At least that's a solvable problem: perform DNSSEC validation (to
> prevent actual attacks) and pretend to clients that you didn't do it (to
> avoid relying on signatures which aren't policy-confiorming).  DNSSEC
> supports that approach quite well for ordinary record types.  It's
> different from the web, where https:// and http:// are not equivalent in
> practice for many domains, and the schema is also visible to _javascript_.

A validating resolver only returns validated results to clients.
There's no "validate but pretend you didn't" mode - if you are a
validating resolver, you either return the record and NOERROR, or you
set SERVFAIL.

Different servers have some ways to override validation, typically on a
per-name basis (so when foo.com breaks their DNSSEC but you have too
many customers that need to get to foo.com to leave it broken).  I'm not
aware of any that any policy hooks to do something similar on an
algorithm basis, and definitely not to do the validation but then
pretend you didn't.  If you want to propose such behavior, you'll need
to get that upstream first (at least in BIND, Unbound, and dnsmasq).


And that behavior would also require that the underlying library be able to expose the fact that the signature validation failed due to local policy, so that the resolver could make use of that information.

It sounds like the proposal here would be:

* Do the validation; if it succeeds, tell the client (if they asked).

* If it fails, but due to local policy, then tell the client no validation was attempted (if they asked).

* If it fails, but not due to local policy, then tell the client SERVFAIL.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux