Return-Path: 
 <hdfs-issues-return-88937-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 913B911B67
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Wed,  2 Jul 2014 02:13:25 +0000 (UTC)
Received: (qmail 83876 invoked by uid 500); 2 Jul 2014 02:13:25 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 83824 invoked by uid 500); 2 Jul 2014 02:13:25 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 83810 invoked by uid 99); 2 Jul 2014 02:13:25 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2014 02:13:25 +0000
Date: Wed, 2 Jul 2014 02:13:25 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12724222.1403902417276.85257.1404267205162@arcas>
In-Reply-To: <JIRA.12724222.1403902417276@arcas>
References: <JIRA.12724222.1403902417276@arcas>
Subject: [jira] [Updated] (HDFS-6605) Client server negotiation of cipher
 suite
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/HDFS-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wang updated HDFS-6605:
------------------------------

    Attachment: hdfs-6605.001.patch

Patch attached. Overall idea:

- Client provides an ordered list of CipherSuites that it likes, the NN chooses the highest priority one that it supports. If there are no valid CipherSuites provided, exception.
- I made the CipherSuite part of CryptoCodec, since that's how you configure which encryption algo to use right now. Since we only support one algo right now, I didn't bother adding NN-side configs for doing smarter validation.
- Added a List<CipherSuite> to the internal create() in ClientProtocol, nothing new exposed, had to mechanically update some unit tests.

> Client server negotiation of cipher suite
> -----------------------------------------
>
>                 Key: HDFS-6605
>                 URL: https://issues.apache.org/jira/browse/HDFS-6605
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: hdfs-6605.001.patch
>
>
> For compatibility purposes, the client and server should negotiate what cipher suite to use based on their respective capabilities. This is also a way for the server to reject old clients that do not support encryption.



--
This message was sent by Atlassian JIRA
(v6.2#6252)