BIND 10 #1689: Handle RRSIG TTL properly when combining multiple RRSIG into a single RRSet

BIND 10 Development do-not-reply at isc.org
Thu Feb 16 10:18:33 UTC 2012


#1689: Handle RRSIG TTL properly when combining multiple RRSIG into a single RRSet
-------------------------------------+-------------------------------------
            Reporter:  shane         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:
           Component:  Unclassified  |                     Keywords:
           Sensitive:  0             |              Defect Severity:
         Sub-Project:  DNS           |  Medium
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Apparently we improperly modify the TTL when we are dealing with RRSIG
 within an RRSet. This came out of discussion on ticket #152:

     MessageImpl::parseSection() would still need to consider RRSIG type
 covered when it combines multiple RRSIGs into a single RRset. That would
 go to a separate ticket.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1689>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list