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

BIND 10 Development do-not-reply at isc.org
Thu Dec 27 22:34:57 UTC 2012


#2586: sqlite3 data source doesn't seem to handle escaped name correctly
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 #2480 revealed a couple of bugs with SQLite3 data source:

 {{{#!cpp
 TEST_P(QueryTest, nxdomainWithNSEC2) {
     // there seems to be a bug in the SQLite3 (or database in general)
 data
     // source and this doesn't work.
 }
 TEST_P(QueryTest, nxdomainWithNSECDuplicate) {
     // there seems to be a bug in the SQLite3 (or database in general)
 data
     // source and this doesn't work.  This is probably the same type of
 bug
     // as nxdomainWithNSEC2
 }
 }}}

 I've not fully looked into the cause, but these cases involve a tricky
 owner name of ").no.example.com." (the first label is normally escaped
 by a backslash in text), and I suspect that's related to this issue.
 And, if so, it may not be easily solved - I suspect that would revisit
 the data representation at the database layer.

 So, in this ticket, I propose we first figure out the real reason.  If
 it turns out to be solvable without touching the database layer, solve
 it within this ticket; otherwise, just record the fact and close the
 ticket.

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


More information about the bind10-tickets mailing list