BIND 10 #2420: allow loading zones containing an orphan RRSIG
BIND 10 Development
do-not-reply at isc.org
Thu Nov 29 23:35:43 UTC 2012
#2420: allow loading zones containing an orphan RRSIG
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: defect | jinmei
Priority: medium | Status:
Component: data source | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20121204
Sub-Project: DNS | Resolution:
Estimated Difficulty: 5 | CVSS Scoring:
Total Hours: 3.32 | Defect Severity: High
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:16 vorner]:
> > > But currently such scenario would throw anyway. I'm not saying this
would be
> > > for the long-term, since there'll be some substantial changes for
merging
> > > RRsets. I thought for now. But if you still think it is not worth
it, then we
> > > can probably leave it as it is.
> >
> > I wouldn't strongly oppose to logging it, but don't see the strong
> > need for it either. At least as long as we throw, it's effectively
> > logged somewhere. So I don't touch it for now.
>
> My point was not about the logging, but about accepting the zone
> where somebody forgot to remove an NSEC3 RRSIG, or something. But it
> should be rare enough, so I won't argue.
I don't understand what this ("somebody forgot...") means in this
context...but anyway, I suspect we'll need to revisit many things when
we are more flexible about load timings anyway, so I'd leave that
particular point to that part of work.
> So I think it can be merged.
Okay, thanks, merge done, closing.
--
Ticket URL: <https://bind10.isc.org/ticket/2420#comment:17>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list