[
https://issues.apache.org/jira/browse/HADOOP-9789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741528#comment-13741528
]
Alejandro Abdelnur commented on HADOOP-9789:
--------------------------------------------
Crossposting my comment in HADOOP-9868,
I'm a bit puzzled by this HADOOP-9789. While I understand the reasoning for it,
doesn't that weaken security? An impersonator can publish an alternate
principal for which it has a keytab for.
> Support server advertised kerberos principals
> ---------------------------------------------
>
> Key: HADOOP-9789
> URL: https://issues.apache.org/jira/browse/HADOOP-9789
> Project: Hadoop Common
> Issue Type: New Feature
> Components: ipc, security
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 3.0.0, 2.1.1-beta
>
> Attachments: HADOOP-9789.2.patch, HADOOP-9789.patch,
> HADOOP-9789.patch, hadoop-ojoshi-datanode-HW10351.local.log,
> hadoop-ojoshi-namenode-HW10351.local.log
>
>
> The RPC client currently constructs the kerberos principal based on the a
> config value, usually with an _HOST substitution. This means the service
> principal must match the hostname the client is using to connect. This
> causes problems:
> * Prevents using HA with IP failover when the servers have distinct
> principals from the failover hostname
> * Prevents clients from being able to access a service bound to multiple
> interfaces. Only the interface that matches the server's principal may be
> used.
> The client should be able to use the SASL advertised principal (HADOOP-9698),
> with appropriate safeguards, to acquire the correct service ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
