Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 28 Mar 2012 01:55:23 +0000 (UTC)
From: "Jakob Homan (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1501676632.26558.1332899723026.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <649383873.29392.1322707060120.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2617) Replaced Kerberized SSL for image
 transfer and fsck with SPNEGO-based solution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240104#comment-13240104 ] 

Jakob Homan commented on HDFS-2617:
-----------------------------------

bq. In the meantime can you answer Alejandro's question wrt we we need to keep the SSL HTTP configuration?
We don't.  As described in the comments above, the posted patch is what we've deployed here, not the final version to be committed.  Removing SSL is a fine thing to do, when I finish the main patch.
                
> Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-2617
>                 URL: https://issues.apache.org/jira/browse/HDFS-2617
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: HDFS-2617-a.patch
>
>
> The current approach to secure and authenticate nn web services is based on Kerberized SSL and was developed when a SPNEGO solution wasn't available. Now that we have one, we can get rid of the non-standard KSSL and use SPNEGO throughout.  This will simplify setup and configuration.  Also, Kerberized SSL is a non-standard approach with its own quirks and dark corners (HDFS-2386).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira