Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 55E08EF50 for ; Wed, 6 Mar 2013 20:04:15 +0000 (UTC) Received: (qmail 68578 invoked by uid 500); 6 Mar 2013 20:04:14 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 68540 invoked by uid 500); 6 Mar 2013 20:04:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 68457 invoked by uid 99); 6 Mar 2013 20:04:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 20:04:14 +0000 Date: Wed, 6 Mar 2013 20:04:14 +0000 (UTC) From: "Oleg Kibirev (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-5316) Provide a secure way to pass password to nodetool, cassandra-cli and other tools MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Oleg Kibirev created CASSANDRA-5316: --------------------------------------- Summary: Provide a secure way to pass password to nodetool, cassandra-cli and other tools Key: CASSANDRA-5316 URL: https://issues.apache.org/jira/browse/CASSANDRA-5316 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.10 Reporter: Oleg Kibirev Currently, if nodetool or cassandra-cli are invoked by another application, plaintext thrift or JMX password are visible to whoever does ps auxww. We need some other method to pass these in, for example a way to read arguments from file or first line of stdin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira