[Unbound-users] [DNSSEC] BIND validates but not Unbound: who is right?

[Casey Deccio]

On Mon, Feb 16, 2015 at 11:34 AM, Stephane Bortzmeyer <bortzmeyer at nic.fr>
wrote:

> With Unbound, I get a SERVFAIL:
>
> ...


> But BIND accepts it (and so does Google Public DNS):
>
> ...

DNSviz, like Unbound, says the domain is broken:
>
> <http://dnsviz.net/d/cepn.asso.fr/VOGwhA/dnssec/>


"Broken" is a loaded term.  There are definitely errors with cepn.asso.fr,
namely that because both algorithms 5 and 8 show up in the DS RRset, the
zone MUST be signed with both, i.e., RRSIGs for each algorithm should be
MUST accompany any RRset in the response.  This is specified in RFC 4035,
Sec 2.2.

However, this requirement is clarified in RFC 6840, Sec. 5.11 as follows:

   This requirement applies to servers, not validators.  Validators
   SHOULD accept any single valid path.  They SHOULD NOT insist that all
   algorithms signaled in the DS RRset work, and they MUST NOT insist
   that all algorithms signaled in the DNSKEY RRset work.

Thus, as Mark pointed out, these particular errors should not affect the
validation of cepn.asso.fr, for validators that understand both algorithms
5 and 8.

Note that DNSViz handles such cases by displaying the errors (i.e., with
the red error sign), but still showing the validation status of the RRsets
as "secure" (denoted by the blue-ish color).

http://dnsviz.net/d/cepn.asso.fr/VOGwhA/dnssec/

However, you can "see" the reason for the requirement of the signer (i.e.,
that it contains RRSIGs for each algorithm in the DS) in the following
example.  Suppose a validator does not support algorithm 5 (e.g., due to
implementation deficiency, administrative policy, or because algorithm has
been declared obsolete for some reason).  The chain of trust now looks like
this:

http://dnsviz.net/d/cepn.asso.fr/VOGwhA/dnssec/?rr=all&a=8&ds=all&ta=.&ta=dlv.isc.org.&tk=

As far as the validator is concerned, there should be a secure path for
both algorithms (as indicated by the algorithms in the DS records).  It
can't choose one or the other because algorithm 5 is not an option.  So it
turns to algorithm 8.  However, because there is no path for algorithm 8,
the chain is broken.

Cheers,
Casey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20150216/be1b2594/attachment.htm>