BIND 10 #2586: sqlite3 data source doesn't seem to handle escaped name correctly

BIND 10 Development do-not-reply at isc.org
Mon Feb 11 11:20:22 UTC 2013


#2586: sqlite3 data source doesn't seem to handle escaped name correctly
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  data source   |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130219
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  4             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => jinmei


Comment:

 hmz, it fails for me:

 {{{
 dnsmessage_test.cc:52: Failure
 Value of: message.getRcode()
   Actual: NOERROR
 Expected: rcode
 Which is: NXDOMAIN
 dnsmessage_test.cc:71: Failure
 Value of: message.getRRCount(Message::SECTION_AUTHORITY)
   Actual: 4
 Expected: nscount
 Which is: 6
 ../../../../src/lib/testutils/dnsmessage_test.h:270: Failure
 Value of: actual_rrsets.size()
   Actual: 4
 Expected: expected_rrsets.size()
 Which is: 6
 Google Test trace:
 ../../../../src/lib/testutils/dnsmessage_test.h:267: Comparing two RRset
 lists:
 Actual:
 example.com. 0 IN SOA . . 1 0 0 0 0
 example.com. 0 IN RRSIG SOA 5 3 3600 20000101000000 20000201000000 12345
 example.com. FAKEFAKEFAKE
 mx.example.com. 3600 IN NSEC &.no.example.com. MX RRSIG NSEC
 mx.example.com. 3600 IN RRSIG NSEC 5 3 3600 20000101000000 20000201000000
 12345 example.com. FAKEFAKEFAKE
 Expected:
 example.com. 0 IN SOA . . 1 0 0 0 0
 example.com. 0 IN RRSIG SOA 5 3 3600 20000101000000 20000201000000 12345
 example.com. FAKEFAKEFAKE
 mx.example.com. 3600 IN NSEC &.no.example.com. MX RRSIG NSEC
 mx.example.com. 3600 IN RRSIG NSEC 5 3 3600 20000101000000 20000201000000
 12345 example.com. FAKEFAKEFAKE
 &.no.example.com. 3600 IN NSEC nz.no.example.com. AAAA RRSIG NSEC
 &.no.example.com. 3600 IN RRSIG NSEC 5 3 3600 20000101000000
 20000201000000 12345 example.com. FAKEFAKEFAKE
 }}}

 (the other one works)

 If we just want to 'fix' the test, we could use '!.no.example.com' instead
 of '%.no.example.com', which passes here. But it would appear there is
 more wrong in the handling here (unpexpected behaviour around '%' in sql
 context is worrying)...

-- 
Ticket URL: <http://bind10.isc.org/ticket/2586#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list