Skip to content
This repository has been archived by the owner on Mar 5, 2021. It is now read-only.

We need a more secure way to save #86

Open
renat-sabitov opened this issue Nov 5, 2014 · 1 comment
Open

We need a more secure way to save #86

renat-sabitov opened this issue Nov 5, 2014 · 1 comment

Comments

@renat-sabitov
Copy link

As for now the only way to save credentials I know is to export AWS env variables and run credulous save
The problem here is that export commands stay in bash history and can be easily recovered.

Expected: when there is no AWS credentials available in environment, credulous save will expect them in the standard input, in the form provided by AWS. For example:

$ credulous save
No AWS credentials found in env, please enter them now:
Access Key ID: AKIAJ43JGF5FHJMXPKTQ
Secret Access Key: gQ00RQOHIwXK+Xb+cBfvSYSDLw+ioc3KeIOPYGw
Enter passphrase: *******
Successfully saved to user@account
@gregwebs
Copy link

gregwebs commented Nov 4, 2016

use a space at the beginning of the line so that they won't be in the history

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants