Bug 1328236 - RFE: Provide hostname's acceptable format
Summary: RFE: Provide hostname's acceptable format
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libosinfo
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabiano Fidêncio
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 19:21 UTC by Fabiano Fidêncio
Modified: 2019-03-29 00:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-29 00:06:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Fabiano Fidêncio 2016-04-18 19:21:02 UTC
Windows is a bit picky with respect to the hostname and doesn't accept any of the following characters: {|}~[\]^':; <=>?@!"#$%`()+/.,*&

Per Zeeshan's suggestion[0], libosinfo could provide this kind of information.

[0]: https://bugzilla.gnome.org/show_bug.cgi?id=765175#c4

Comment 1 Christophe Fergeau 2016-04-19 09:10:04 UTC
When I read 'hostname' I'm thinking of some URL-like think (ie what you get from the 'hostname' command on a linux machine). Of the forbidden characters you listed, I think only '.' would be valid for such a hostname. Maybe it's enough to document which characters are valid for 'hostname'? Or does it have a different meaning in libosinfo?

Comment 2 Fabiano Fidêncio 2016-04-19 11:09:31 UTC
(In reply to Christophe Fergeau from comment #1)
> When I read 'hostname' I'm thinking of some URL-like think (ie what you get
> from the 'hostname' command on a linux machine). Of the forbidden characters
> you listed, I think only '.' would be valid for such a hostname. Maybe it's
> enough to document which characters are valid for 'hostname'? Or does it
> have a different meaning in libosinfo?

hostname is the name you give to your computer. Windows is used to call it ComputerName.
All these characters are invalid for Windows (according to the Windows 8.1 installer).

Comment 4 Cole Robinson 2019-03-29 00:06:04 UTC
I have moved this to the upstream tracker: https://gitlab.com/libosinfo/libosinfo/issues/21


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