BIND 10 #2503: Problem in inmem NSEC3 denial of existence handling
BIND 10 Development
do-not-reply at isc.org
Mon Dec 10 11:26:02 UTC 2012
#2503: Problem in inmem NSEC3 denial of existence handling
-------------------------------------+-------------------------------------
Reporter: jelte | Owner: muks
Type: defect | Status:
Priority: medium | reviewing
Component: data source | Milestone:
Keywords: | Sprint-20121218
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 3 | Defect Severity: Low
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: UnAssigned => muks
Comment:
Replying to [comment:6 muks]:
> I'm guessing the second `SOA` in the zone is also a copy-paste error.
not related to the review or anything else in this ticket, but no, that
was not a copy/paster error; the second SOA is part of the transfer
protocol :)
Like in 2504 I replaced the zone contents with a zone 'example.com'
instead of my zone origin.
And some comments:
zone_data.h:
The new parameter (zone_name) has no doxygen description. (also, the
parameter name is zone_name in the header, but zone_origin in the
implementation. Not a problem in practice, but inconsistent and
potentially confusing)
I'm wondering if we shouldn't also test the case where the name exists but
the type does not (in retrospect, maybe the same goes for 2504).
Also, I think we should probably mention that this specifically fixes a
bug in the case where the zone only contains one name (also
retrospectively for 2504).
--
Ticket URL: <https://bind10.isc.org/ticket/2503#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list