Bug 39364 – Hostname syntax-check doesnt allow numeric subdomains

Bug 39364 - Hostname syntax-check doesnt allow numeric subdomains


Summary:	Hostname syntax-check doesnt allow numeric subdomains

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-09-18 12:07 CEST by Dirk Ahrnke
Modified:	2019-01-03 07:16 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Ahrnke 2015-09-18 12:07:39 CEST

reported in http://forum.univention.de/viewtopic.php?t=4375

Repro:
root@test:~# hostname -f
test.123.mydomain.intranet
root@test:~# udm shares/share create --position cn=shares,$(ucr get ldap/base) --set name=test --set host=$(hostname -f) --set path=/test 
E: Invalid Syntax: Host: Not a valid FQDN

I dont see a reason in RFC 1035 why this FQDN is invalid.

Comment 1 Daniel Tröder

2015-09-18 12:16:16 CEST

Maybe testing according to (deprecated) RFC 952: "The first character must be an alpha character."  https://tools.ietf.org/html/rfc952 → ASSUMPTIONS

Comment 2 Stefan Gohmann

2019-01-03 07:16:27 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.