BIND 10 #1516: Where did AUTH_UNSUPPORTED_OPCODE come from?

BIND 10 Development do-not-reply at isc.org
Fri Jan 10 02:46:41 UTC 2014


#1516: Where did AUTH_UNSUPPORTED_OPCODE come from?
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  low           |                       Status:
           Component:  b10-auth      |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20131015
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by muks):

 I think no `ChangeLog` update is necessary for this ticket too, as it adds
 extra information about the source. But in any case, if we want it, the
 `ChangeLog` message is:
 {{{
 XYZ.    [func]          muks
         b10-auth now additionally logs the source address and port when
         DNS messages with unsupported opcodes are received.
         (Trac #1516, git ...)
 }}}

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


More information about the bind10-tickets mailing list