[
https://issues.apache.org/jira/browse/HDFS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894238#action_12894238
]
Jakob Homan commented on HDFS-1150:
-----------------------------------
bq. The point is that we already "support" the SELinux way
If your "support" for security comes with quotation marks, you've got a
problem.
bq. Think of it like
i.already.secured.my.datanode.port.with.some.external.mechanism
This is a more reasonable way of arguing your request. Essentially it's the
beginning of a pluggable system where the verification is Ops' word that
they've taken care of this security hole. My concern remains that this provides
no way for a running cluster to realize it's been misconfigured, although I've
been thinking we need a security info page on the NN/JT (along with HADOOP-6823
and HADOOP-6822) and this could be displayed there (although the danger for
non-updated, erroneous configs scattered around the cluster still remains).
Administrators would need to affirmatively decline this type of protection,
perhaps with a value to the key of "No, thanks."
> Verify datanodes' identities to clients in secure clusters
> ----------------------------------------------------------
>
> Key: HDFS-1150
> URL: https://issues.apache.org/jira/browse/HDFS-1150
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: data-node
> Affects Versions: 0.22.0
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Attachments: commons-daemon-1.0.2-src.tar.gz,
> HDFS-1150-BF-Y20-LOG-DIRS-2.patch, HDFS-1150-BF-Y20-LOG-DIRS.patch,
> HDFS-1150-BF1-Y20.patch, hdfs-1150-bugfix-1.1.patch,
> hdfs-1150-bugfix-1.2.patch, hdfs-1150-bugfix-1.patch, HDFS-1150-trunk.patch,
> HDFS-1150-Y20-BetterJsvcHandling.patch, HDFS-1150-y20.build-script.patch,
> HDFS-1150-Y20S-ready-5.patch, HDFS-1150-Y20S-ready-6.patch,
> HDFS-1150-Y20S-ready-7.patch, HDFS-1150-Y20S-ready-8.patch,
> HDFS-1150-Y20S-Rough-2.patch, HDFS-1150-Y20S-Rough-3.patch,
> HDFS-1150-Y20S-Rough-4.patch, HDFS-1150-Y20S-Rough.txt
>
>
> Currently we use block access tokens to allow datanodes to verify clients'
> identities, however we don't have a way for clients to verify the
> authenticity of the datanodes themselves.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
