BIND 10 #3340: DHO_HOST_NAME is defined as a string option, b10-dhcp4 treats it as a custom option

[BIND 10 Development]

#3340: DHO_HOST_NAME is defined as a string option, b10-dhcp4 treats it as a
custom option
-------------------------------------+-------------------------------------
                   Reporter:  tmark  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  DHCP-
                   Priority:  high   |  Kea0.9-alpha
                  Component:  dhcp-  |              Keywords:
  ddns                               |             Sensitive:  0
               CVSS Scoring:         |           Sub-Project:  DHCP
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Logic in !Dhcpv4Srv::processClientName() looks for the DHO_HOST_NAME
 option as a !OptionCustom, however, libdhcp++ defines it as and handles it
 as a !OptionString.

 When this logic is passed a packet that was actually unpacked (i.e a live
 packet received from Scapy or from a buffer), the option itself exists but
 the dynamic cast used by the method fails.

 Unit tests for this are currently passing because the query packets add
 the host name option as a OptionCustom but not packed and unpacked.

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