BIND 10 #1936: What packet resulted in AUTH_PACKET_PARSE_ERROR ?

BIND 10 Development do-not-reply at isc.org
Fri May 11 12:55:41 UTC 2012


#1936: What packet resulted in AUTH_PACKET_PARSE_ERROR ?
--------------------------------------------+----------------------------
                   Reporter:  jreed         |                 Owner:
                       Type:  enhancement   |                Status:  new
                   Priority:  medium        |             Milestone:
                  Component:  Unclassified  |            Resolution:
                   Keywords:                |             Sensitive:  0
            Defect Severity:  N/A           |           Sub-Project:  DNS
Feature Depending on Ticket:                |  Estimated Difficulty:  0
        Add Hours to Ticket:  0             |           Total Hours:  0
                  Internal?:  0             |
--------------------------------------------+----------------------------
Changes (by shane):

 * type:  defect => enhancement
 * milestone:  New Tasks =>


Comment:

 Interesting. This is a DEBUG message, so this error is not something that
 we would normally see. However, it may be interesting. (I think the
 particular message indicates that there was not enough data in the packet
 considering the length used for the RDATA packet.)

 We can't really display too much about the packet, since the parse failed.
 Perhaps the right thing to do is add a facility for the administrator to
 log bogus packets? (Ultimately this is exactly right for a hook, but
 perhaps we can get something sooner?)

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


More information about the bind10-tickets mailing list