Opened 19 months ago

Last modified 17 months ago

#5680 closed enhancement

kea-dhcp4 server needs to support configurable client hostname sanitization — at Version 5

Reported by: tmark Owned by: tmark
Priority: high Milestone: Kea1.5
Component: dhcp4 Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by tmark)

The Infoblox SOW requires the ability to sanitize client host name values, sent by DHCPv4 clients, prior to using them to form the FQDN for DNS updates. Specifically, there should be two configuration parameters:

  1. A regular expression (e.g. [A-za-z0-9]-) which describes the allowed characters
  2. A replacement for characters that are disallowed (e.g. _ by -)

Does not apply to v6, or to v4 FQDN option values, as per RFC they cannot contain non-compliant characters.

Subtickets

Change History (5)

comment:1 Changed 19 months ago by tmark

  • Owner set to tmark
  • Status changed from new to assigned

comment:2 Changed 19 months ago by fdupont

  • Description modified (diff)

comment:3 Changed 19 months ago by fdupont

BTW bind9 has at least the 1 in src/lib/name.c dns_name_ishostname()... 2 is more challenging because hostname allowed character set is *very* limited (e.g. no ?, - illegal in first position, etc).

comment:4 Changed 19 months ago by fdupont

  • Summary changed from kea-dhcp4/6 servers need to support confiugrable client hostname sanitization to kea-dhcp4/6 servers need to support configurable client hostname sanitization

comment:5 Changed 19 months ago by tmark

  • Component changed from Unclassified to dhcp4
  • Description modified (diff)
  • Summary changed from kea-dhcp4/6 servers need to support configurable client hostname sanitization to kea-dhcp4 server needs to support configurable client hostname sanitization
Note: See TracTickets for help on using tickets.