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

Update the docs to make WSL usage more clear #736

Closed
3 tasks
epicserve opened this issue Mar 1, 2021 · 13 comments
Closed
3 tasks

Update the docs to make WSL usage more clear #736

epicserve opened this issue Mar 1, 2021 · 13 comments
Labels

Comments

@epicserve
Copy link

  • I am using the latest release of AWS Vault
  • I have provided my .aws/config (redacted if necessary)
  • I have provided the debug output using aws-vault --debug (redacted if necessary)
$ aws-vault --debug
2021/03/01 16:56:08 aws-vault v6.2.0
$ cat ~/.aws/config
[default]
region=us-east-1

[profile admin]
source_profile=work
parent_profile=work
role_arn=arn:aws:iam::<redacted>:role/OEIEAdmin

[profile dev]
region=us-east-1
source_profile=work
parent_profile=work
role_arn=arn:aws:iam::<redacted>:role/Developer

[profile work]
mfa_serial=<redacted>

When reading through the README it's not clear which backend you're supposed to use with Ubuntu under Windows WSL 2. I was able to get the file backend to work, however, it doesn't seem like the file backend can remember your password for a given period of time like I was used to under macOS.

@paulmchenry
Copy link

I've also been having problems with this and was wondering if I'm supposed to be prompted to enter credentials with every aws-vault exec command I use; this is what I am currently seeing and it seems incorrect.

@ibuseyo
Copy link

ibuseyo commented Apr 5, 2021

Yes. Could we have some support of backend for wsl2. I am getting
Specified keyring backend not available, try --help

@mtibben
Copy link
Member

mtibben commented Apr 6, 2021

PRs welcome

@epicserve
Copy link
Author

@mtibben,

Is the file backend what is recommended when using WSL 2/ubuntu or is it something else? I would need to know that before creating a PR.

@mtibben
Copy link
Member

mtibben commented Apr 8, 2021

I don't use windows, I have no recommendation

@ibuseyo
Copy link

ibuseyo commented Apr 9, 2021

I got it running setting pass as the backend password manager.

export AWS_VAULT_BACKEND="pass"

@warwickgrigg
Copy link

The instructions in #683 for pass and gpg work for me when combined with:

export AWS_VAULT_BACKEND=pass
export GPG_TTY="$( tty )"

@dannysauer
Copy link
Contributor

I've been using X410 as an X server and have installed gnome-keyring in my WSL image, and that backend works ok with both this and saml2aws. I haven't yet figured out how to make a single keyring instance live under the command line, however; it wants dbus in order to work. Same is true of the KDE keyring program. That Open Desktop keyring standard is available, though... So if someone wants to look around for a console-friendly keyring option, or maybe figure out how o get a DBUS session working without a traditional Linux desktop environment, that might give a start.

@stale
Copy link

stale bot commented Jan 3, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 3, 2022
@dannysauer
Copy link
Contributor

Docs have not been updated. Issue is not stale.

@stale stale bot removed the stale label Jan 3, 2022
@MikeKroell
Copy link

I am interested in this as well. We use gimme-aws-creds for AWS authentication and the keyring is not working for us either. I;m not a developer, but interested in having a solution.

@SimonLafrikh
Copy link

If you are on windows 11 and on the supported build you can install gnome keyring on wsl and use aws-vault like normal.
https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps

Make sure to update your GPU drivers to the latest version that includes this feature.

@stale
Copy link

stale bot commented Nov 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 2, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants