You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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: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.
The text was updated successfully, but these errors were encountered: