-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Allow overriding SSH Agent socket path #3795
Labels
Comments
hifi
added a commit
to hifi/keepassxc
that referenced
this issue
Nov 5, 2019
hifi
added a commit
to hifi/keepassxc
that referenced
this issue
Nov 6, 2019
hifi
added a commit
to hifi/keepassxc
that referenced
this issue
Nov 6, 2019
hifi
added a commit
to hifi/keepassxc
that referenced
this issue
Nov 12, 2019
hifi
added a commit
to hifi/keepassxc
that referenced
this issue
Nov 16, 2019
droidmonkey
pushed a commit
to hifi/keepassxc
that referenced
this issue
Jan 27, 2020
droidmonkey
pushed a commit
to hifi/keepassxc
that referenced
this issue
Jan 27, 2020
droidmonkey
pushed a commit
to hifi/keepassxc
that referenced
this issue
Jan 28, 2020
droidmonkey
pushed a commit
that referenced
this issue
Jan 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A lot of people start the agent outside the effective session on Linux from an interactive shell. It isn't obvious why KeePassXC can't see the environment variable required to access it.
Possible Solution
Add socket path override option to SSH Agent settings page. Additionally show the effective path that KeePassXC is currently picking up from the environment.
The text was updated successfully, but these errors were encountered: