[jira] [Updated] (YARN-2677) registry punycoding of usernames doesn't fix all usernames to be DNS-valid
[
https://issues.apache.org/jira/browse/YARN-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated YARN-2677:
-
Attachment: YARN-2677-002.patch
Updated patch which also converts usernames to lower case (english locale).
This handles names like {{Administrator}} which you can see on windows
registry punycoding of usernames doesn't fix all usernames to be DNS-valid
--
Key: YARN-2677
URL: https://issues.apache.org/jira/browse/YARN-2677
Project: Hadoop YARN
Issue Type: Sub-task
Components: api, resourcemanager
Affects Versions: 2.6.0
Reporter: Steve Loughran
Assignee: Steve Loughran
Attachments: YARN-2677-001.patch, YARN-2677-002.patch
The registry has a restriction DNS-valid names only to retain the future
option of DNS exporting of the registry.
to handle complex usernames, it punycodes the username first, using Java's
{{java.net.IDN}} class.
This turns out to only map high unicode- ASCII, and does nothing for
ascii-but-invalid-hostname chars, so stopping users with DNS-illegal names
(e.g. with an underscore in them) from being able to register
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-2677) registry punycoding of usernames doesn't fix all usernames to be DNS-valid
[
https://issues.apache.org/jira/browse/YARN-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated YARN-2677:
Hadoop Flags: Reviewed
+1 for the patch. I verified this on both Mac and Windows. Thanks, Steve!
registry punycoding of usernames doesn't fix all usernames to be DNS-valid
--
Key: YARN-2677
URL: https://issues.apache.org/jira/browse/YARN-2677
Project: Hadoop YARN
Issue Type: Sub-task
Components: api, resourcemanager
Affects Versions: 2.6.0
Reporter: Steve Loughran
Assignee: Steve Loughran
Attachments: YARN-2677-001.patch, YARN-2677-002.patch
The registry has a restriction DNS-valid names only to retain the future
option of DNS exporting of the registry.
to handle complex usernames, it punycodes the username first, using Java's
{{java.net.IDN}} class.
This turns out to only map high unicode- ASCII, and does nothing for
ascii-but-invalid-hostname chars, so stopping users with DNS-illegal names
(e.g. with an underscore in them) from being able to register
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-2677) registry punycoding of usernames doesn't fix all usernames to be DNS-valid
[
https://issues.apache.org/jira/browse/YARN-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated YARN-2677:
-
Attachment: YARN-2677-001.patch
patch that
# stops checking for validity of entries against DNS pattern
# strips out kerberos realm/host info, so that {{hbase/host@REALM}} maps down
to {{hbase}}. UGI should have been doing this in its shortname logic, but
clearly not
registry punycoding of usernames doesn't fix all usernames to be DNS-valid
--
Key: YARN-2677
URL: https://issues.apache.org/jira/browse/YARN-2677
Project: Hadoop YARN
Issue Type: Sub-task
Components: api, resourcemanager
Affects Versions: 2.6.0
Reporter: Steve Loughran
Assignee: Steve Loughran
Attachments: YARN-2677-001.patch
The registry has a restriction DNS-valid names only to retain the future
option of DNS exporting of the registry.
to handle complex usernames, it punycodes the username first, using Java's
{{java.net.IDN}} class.
This turns out to only map high unicode- ASCII, and does nothing for
ascii-but-invalid-hostname chars, so stopping users with DNS-illegal names
(e.g. with an underscore in them) from being able to register
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
