Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 20 Jun 2016 14:22:05 +0000 (UTC)
From: "Mobin Ranjbar (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12980872.1466432497000.44841.1466432525331@Atlassian.JIRA>
In-Reply-To: <JIRA.12980872.1466432497000@Atlassian.JIRA>
References: <JIRA.12980872.1466432497000@Atlassian.JIRA> <JIRA.12980872.1466432497195@arcas>
Subject: [jira] [Created] (HADOOP-13295) Possible Vulnerability in DataNodes
 via SSH
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 20 Jun 2016 14:22:09 -0000

Mobin Ranjbar created HADOOP-13295:
--------------------------------------

             Summary: Possible Vulnerability in DataNodes via SSH
                 Key: HADOOP-13295
                 URL: https://issues.apache.org/jira/browse/HADOOP-13295
             Project: Hadoop Common
          Issue Type: Bug
            Reporter: Mobin Ranjbar


I suspected something weird in my Hadoop cluster. When I run datanodes, after a while my servers(except namenode) will be down for SSH Max Attempts. When I checked the 'systemctl status ssh', I figured out there are some invalid username/password attempts via SSH and the SSH daemon blocked all incoming connections and I got connection refused.

I have no problem when my datanodes are not running.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org