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.

Sign up for GitHub

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

Jump to bottom

kheetun should be able to use a locked explicitly set key when the key is already unlocked in the ssh agent #18

Open
jklippel opened this issue Mar 2, 2017 · 0 comments
Open

kheetun should be able to use a locked explicitly set key when the key is already unlocked in the ssh agent #18

jklippel opened this issue Mar 2, 2017 · 0 comments

Comments

@jklippel
Copy link

jklippel commented Mar 2, 2017

kheetun should be able to use a locked explicitly set key when the key is already unlocked in the ssh agent

Currently the explicitly set key is used. Thus kheetun is unable to access the key (see different/related issue #17), despite the fact that the very same key is unlocked available via the agent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jklippel