BIND 10 #2786: DHCPv4: domain-name option must be encoded as text and NOT as FQDN
BIND 10 Development
do-not-reply at isc.org
Mon May 13 17:30:31 UTC 2013
#2786: DHCPv4: domain-name option must be encoded as text and NOT as FQDN
-------------------------------------+-------------------------------------
Reporter: marcin | Owner:
Type: defect | UnAssigned
Priority: high | Status:
Component: dhcp4 | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-DHCP-20130523
Sub-Project: DHCP | Resolution:
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity:
| Medium
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by marcin):
* owner: marcin => UnAssigned
* status: assigned => reviewing
Comment:
The domain-name option is now encoded using simple string. Since, there
are quite a few options which have similar structure, I also derived new
class !''!OptionString!'' which represents an option carrying a single
string value with the length of at least 1 character.
The proposed !ChangeLog entry is:
{{{
6XX. [bug] marcin
b10-dhcp4: Fixed a bug whereby the domain-name option was encoded
as FQDN (using technique described in RFC1035) instead of a
string.
Also, created new class which represents an option carrying a
single
string value. This class is now used for all standard options of
this kind.
(Trac #2786, git abc)
}}}
Please review.
--
Ticket URL: <http://bind10.isc.org/ticket/2786#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list