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
aws-vault >= 5.1 fails to open keyring on linux #513
Comments
Unlocking also works fine using the keyring CLI directly:
|
Please try with the latest release - v5.1.0 is not the latest |
Sorry if I wasn't clear. This happens with every version since v5.1.0, including v5.2.0. |
I'm running into the same issue, I believe. When using commands like |
I'm on macOS, so anyone on Linux feel free to jump in and help here |
Could you create a branch with more debug output? I'm happy to build from source and test to get this fixed. |
Yay I'm learning go! :) Couldn't wait and figured out how to run it in gdb. It seems that And that also seems to be consistent with the keyring CLI tool:
|
Also, once the keyring is unlocked, -list-keys works as expected. And it gets better. If I lock the keyring again, -list-keys still works! Only if kill gnome-keyring-daemon (the provider of org.freedesktop.secrets.service), -list-keys returns empty strings again. |
I opened an issue upstream to clarify if gnome-keyring's behaviour is intended. |
Hi I am having the same issue with v5.1.2. Seems to be sending empty strings. |
I have a fix, brushing up the tests and will post it shortly. |
Fixed in v5.2.1 |
Nice digging @christophgysin, thanks! |
.aws/config
(redacted if necessary)aws-vault --debug
(redacted if necessary)I'm using the secret-service credential provider on ArchLinux. Recent versions of aws-vault fail to unlock the keyring. If I manually unlock the keyring, everything works again as expected.
It seems that this was introduced by 1c0b58a.
The text was updated successfully, but these errors were encountered: