Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C2EA7200C4E for ; Fri, 21 Apr 2017 19:59:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C1FB5160B86; Fri, 21 Apr 2017 17:59: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 06941160BAF for ; Fri, 21 Apr 2017 19:59:07 +0200 (CEST) Received: (qmail 9986 invoked by uid 500); 21 Apr 2017 17:59:07 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 9965 invoked by uid 99); 21 Apr 2017 17:59:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2017 17:59:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C81591AFC0D for ; Fri, 21 Apr 2017 17:59:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id b2bducnZ4wxx for ; Fri, 21 Apr 2017 17:59:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8FC9261EC8 for ; Fri, 21 Apr 2017 17:59:05 +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 16A88E0D85 for ; Fri, 21 Apr 2017 17:59:05 +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 519FC21D62 for ; Fri, 21 Apr 2017 17:59:04 +0000 (UTC) Date: Fri, 21 Apr 2017 17:59:04 +0000 (UTC) From: "Sumit Mohanty (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 21 Apr 2017 17:59:08 -0000 [ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17666: ----------------------------------- Fix Version/s: 2.4.3 > Ambari agent can't start when TLSv1 is disabled in Java security > ---------------------------------------------------------------- > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent > Affects Versions: 2.2.0 > Reporter: Tuong Truong > Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0, 2.4.3 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 explicit force the SSL protocol to TLSv1 in ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, this setting in effect whenever web_alert pacackged is loaded (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)