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

Idea: put generated passwords in a Vault kv store? #1

Open
brucellino opened this issue Oct 23, 2022 · 1 comment
Open

Idea: put generated passwords in a Vault kv store? #1

brucellino opened this issue Oct 23, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@brucellino
Copy link

Love this. I generated passwords for a long time using </dev/urandom tr -dc 'A-Za-z0-9!"}?!*)' | head -c 32 that I ended up putting in a 😱 file.

I have moved them to a Vault instance at home, but I still need to generate them and grasp seems pretty cool.

I immediately thought about extending it to use the Vault API as a persistent secure storage.

creating:
phrase->grasp->generates secret password->puts it in vault
retrieving:
phrase->grasp->maps to kv key in vault->retrieves secret password

This way, the user would only need to remember the phrase and not the password.

Any thoughts?

@lucasepe
Copy link
Owner

Thanks!
...and...great idea! ... maybe letting the user to choose whether to just print the password or copying it into clipboard or to store it in Vault.

Besides your idea just triggered me with some more abstract extension 😄 ...

What if we could try to implement something like hashicorp plugins using RPC in order to implement different backend destinations ... (terminal will be the default, but we can thing at Vault, clipboard, SQL, etc. etc.)

@lucasepe lucasepe added the enhancement New feature or request label Oct 23, 2022
@lucasepe lucasepe self-assigned this Oct 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants