Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(GH-1106) Hide sensitive data in choco apikey call output #1122

Conversation

paulhunttech
Copy link

@paulhunttech paulhunttech commented Jan 3, 2017

Closes #1106

Replaced plain text api key output with "(Authenticated)" where the api key is not null or whitespace.

@paulhunttech paulhunttech changed the title Woodburysoft/hide credentials in choco apikey call output Hide credentials in choco apikey call output Jan 3, 2017
@paulhunttech paulhunttech changed the title Hide credentials in choco apikey call output Hide sensitive data in choco apikey call output Jan 3, 2017
@ferventcoder
Copy link
Member

Looks good, can you squash this down to one commit?

@ferventcoder ferventcoder changed the title Hide sensitive data in choco apikey call output (GH-1106) Hide sensitive data in choco apikey call output Jan 3, 2017
Copy link
Member

@ferventcoder ferventcoder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Squash changes to one commit, maybe remove the merge commit.

@paulhunttech paulhunttech force-pushed the woodburysoft/HideCredentialsInChocoApikeyCallOutput branch from 611e038 to 7ff013f Compare January 3, 2017 19:44
Previously the 'choco apikey' command wrote the API key for a source to the output in plain text which is a potential security issue. Update the generated output to "(Authenticated)" if the API key is not null or whitespace.

Replaced credentials from apikey output and replaced with "(Authenticated)".
@paulhunttech paulhunttech reopened this Jan 3, 2017
@paulhunttech
Copy link
Author

Had some fun & games squashing as I'd never done it before but I believe it's right now.

@ferventcoder
Copy link
Member

Merged into stable at fe55f47.

Thanks for your contribution! This will be in the 0.10.4 release!

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

Successfully merging this pull request may close these issues.

2 participants