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

Allow symlinks from .ssh to .skm #38

Closed
ZinoKader opened this issue Dec 29, 2021 · 2 comments
Closed

Allow symlinks from .ssh to .skm #38

ZinoKader opened this issue Dec 29, 2021 · 2 comments

Comments

@ZinoKader
Copy link

ZinoKader commented Dec 29, 2021

Very nice tool, thank you!

I have a small suggestion for how I think the file handling around the keys should work
I and I suppose most other people prefer not moving the ssh keys into .skm, but rather to have symbolic links to the ssh keys created in .skm. Right now, I have the original keys in .skm and symlink them to .ssh but prefer to have it the other way around.

I tried to have the original files in .ssh and symlink them to .skm, but this resulted in the files not being readable:

✔ Found 2 SSH key(s)!

Failed to read  /Users/[[redacted]]/.skm/[[redacted]]@[[redacted]].com/id_rsa.pub
	[[redacted]]@[[redacted]].com	[]	[]
Failed to read  /Users/[[redacted]]/.skm/[[redacted]]@[[redacted]].com/id_rsa.pub
	[[redacted]]@[[redacted]].com []	[]

I suppose currently symlinks are not resolved. By following symlinks, this should be possible to do if one would want to, without changing the default behavior of skm.

@TimothyYe
Copy link
Owner

TimothyYe commented Dec 29, 2021

I think there is another solution you can try with:
https://github.com/TimothyYe/skm#customized-ssh-key-store-path

I haven't tried yet, you can try to set SKM_STORE_PATH with the path of your .ssh directory.

@ZinoKader
Copy link
Author

Works great, thank you! You can close this, I totally missed the option to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants