[WHIRR-642] Whirr writes the AWS Secret key to the stdout. is it an unforeseen byproduct or intended behavior?

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.1, 0.9.0
• Fix Version/s: 0.8.1
• Component/s: cli

Environment

OSX Mountain Lion

• Assignee: Steve Loughran
• Reporter: P Mohan
• Created: 21/Aug/12 23:36
• Updated: 25/Sep/12 11:19
• Resolved: 20/Sep/12 21:00

Description

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 stdout.

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 ?