From hdfs-issues-return-209716-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Feb 7 20:30:08 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 2E7D718065B for ; Wed, 7 Feb 2018 20:30:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1E7F2160C5B; Wed, 7 Feb 2018 19:30:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 669DB160C3A for ; Wed, 7 Feb 2018 20:30:07 +0100 (CET) Received: (qmail 77770 invoked by uid 500); 7 Feb 2018 19:30:06 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 77759 invoked by uid 99); 7 Feb 2018 19:30:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2018 19:30:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E0846C2F8F for ; Wed, 7 Feb 2018 19:30:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id kgX2KFGKpPYz for ; Wed, 7 Feb 2018 19:30:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 96E5D5FBF5 for ; Wed, 7 Feb 2018 19:30:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6216BE0295 for ; Wed, 7 Feb 2018 19:30:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id EE8DC24133 for ; Wed, 7 Feb 2018 19:30:00 +0000 (UTC) Date: Wed, 7 Feb 2018 19:30:00 +0000 (UTC) From: "Jitendra Nath Pandey (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13081) Datanode#checkSecureConfig should check HTTPS and SASL encryption MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-13081?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1635= 5938#comment-16355938 ]=20 Jitendra Nath Pandey commented on HDFS-13081: --------------------------------------------- {quote}Delegation tokens send passwords in the clear over http. =C2=A0Webhd= fs is at high risk. {quote} That is a valid point. That explains=C2=A0why check for HTTPS was added in = the first place. It should be documented in javadocs. IIUC the required checks are following: 1) For RPC: It should be either a privileged port or must use SASL for mutu= al authentication. 2) For HTTP: It should be either a privileged port or must use HTTPS=C2=A0 However a combination like privileged port for HTTP and SASL for RPC should= also work.=C2=A0 The advantage of SASL is that it allows qop negotiation and different clien= ts can choose encryption depending on where they are connecting from and se= nsitivity of data. [~daryn], what are your thoughts on having privileged port for HTTP with SA= SL for RPC? > Datanode#checkSecureConfig should check HTTPS and SASL encryption > ----------------------------------------------------------------- > > Key: HDFS-13081 > URL: https://issues.apache.org/jira/browse/HDFS-13081 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode, security > Affects Versions: 3.0.0 > Reporter: Xiaoyu Yao > Assignee: Ajay Kumar > Priority: Major > Attachments: HDFS-13081.000.patch > > > Datanode#checkSecureConfig currently check the following to determine if = secure datanode=C2=A0is enabled.=C2=A0 > # The server has bound to privileged ports for RPC and HTTP via SecureDa= taNodeStarter. > # The configuration enables SASL on DataTransferProtocol and HTTPS (no p= lain HTTP) for the HTTP server. The SASL handshake guarantees authenticatio= n of the RPC server before a client transmits a secret, such as a block acc= ess token. Similarly, SSL guarantees authentication of the > HTTP server before a client transmits a secret, such as a delegation tok= en. > For the 2nd case, HTTPS_ONLY means all the traffic between=C2=A0REST clie= nt/server will be encrypted. However, the logic to check only if SASL prope= rty resolver is configured does not mean server requires an encrypted RPC.= =C2=A0 > This ticket is open to further check and ensure datanode=C2=A0SASL proper= ty resolver has a QoP that includes auth-conf(PRIVACY). Note that the SASL = QoP (Quality of Protection) negotiation may drop RPC protection level from = auth-conf(PRIVACY) to auth-int(integrity) or auth(authentication) only, whi= ch should be fine by design. > =C2=A0 > cc: [~cnauroth] ,=C2=A0[~daryn], [~jnpandey] for additional feedback. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org