P Mohan created WHIRR-642:
-----------------------------
Summary: Whirr writes the AWS Secret key to the stdout. is it an
unforeseen byproduct or intended behavior?
Key: WHIRR-642
URL: https://issues.apache.org/jira/browse/WHIRR-642
Project: Whirr
Issue Type: Bug
Components: cli
Affects Versions: 0.7.1
Environment: OSX Mountain Lion
Reporter: P Mohan
Priority: Minor
I used Whirr to launch a CDH cluster. Towards the end the whirr output has the
AWS secret key in plain text as shown below.
fs.s3.awsSecretAccessKey=qBqa*********************************, fs.s3.a
wsAccessKeyId=AKIA*****************,
hadoop.rpc.socket.factory.class.default=org.apache.hadoop.net.SocksSocketFactory,
fs.default.name=hdfs://ec2-**********.compute-1.amazonaws.c
om:8020/, fs.s3n.awsSecretAccessKey=qBqaott5*************************}}
is this intended behavior. Would it be not better to mask or not print the AWS
Secret key to the stdin.
One gd thing i noticed is that the AWS Secret Key is not written to the
whirr.log file. Can we not have the same behavior for the stdout as well ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
