-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
How to import external keys to Vault #85
Comments
Hello, I do not have the Vault CLI at hand at the moment but you need to pass the key as a string, the CLI cannot work from a file path. Something like |
@lucaspwk
|
For both cases does not work. Seems the variable is not receiving the correct info.
Using print I can see the whole block but with some errors on stdout.. Any other idea how to convert the text/key to string? Or there is another way to import keys? How do you do that? |
I did a python script to convert the text file and I did the call to vault using curl but I'm receiving error to private key:
If you want to check, here is how I export my private key from GPG:
|
The key seems to be protected by a passphrase can you try without it? |
Yes there is a passphrase. Is not possible to import if is protected by passphrase? Also, can I import public keys as well? |
No it's not possible. The plugin needs to have access to the private part of the key.
No. If you only want to do operations with the public part of a key you have a better time to do them directly instead of calling Vault. |
Hello,
First I would like to thank for you this plugin. Amazing work
My issue is just a question/doubt that I'm facing to use it. I don't know how to import a external pgp key on vault. What should I do? I already exported on GPG and I have the ascii armored key in a file. I tried on that ways:
vault write gpg/keys/test --generate=false --key=./file_private.key
Can you help me on that?
Thanks,
Lucas.
The text was updated successfully, but these errors were encountered: