-
Notifications
You must be signed in to change notification settings - Fork 801
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
Unable to decrypt credentials file when using pass backend #1230
Comments
Same for me, i get below error gpg: XXXXXXXXXXXXXXXXXXXXXXXXX: skipped: No public ke |
Despite what I stated above I think this is some how related to #686. I think |
changed Command = export AWS_VAULT_BACKEND=file |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Yes, v7.2.0 installed via
asdf
..aws/config
(redacted if necessary)AWS_CONFIG_FILE="${XDG_CONFIG_HOME}/aws/config"
I also have the following environment variables set:
My profile credentials are stored in
aws-vault --debug
(redacted if necessary)I checked #686 and I already had
$GPG_TTY=$(tty)
set and exported so not the same issue. Now my primary GPG key is stored in a Trezor model-T and am prompted on it when I need to decrypt a file in my password-store. This works well when not usingaws-vault
because my password-store was initialised with my TREZOR-based GPG identity.However, you can see from the
aws-vault
command output above it is not working whenaws-vault
is in the loop. What is the significance of the--prompt
flag? I understand from #1185 one use to be able to set this to "pass". Could the removal of this option be why I don't get prompted on my hardware based token.I don't think the
mfa_process
option will work as I'm not usingpass
to generate an otp. I have MFA access set up on my two profiles and am using a software based MFA device. If I include themfa_serial
identifier in my profile I get prompted to enter the otp but it still doesn't work.Any ideas? Thanks for your time.
The text was updated successfully, but these errors were encountered: