Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Failure to authenticate with ssh when using :private-key-path (as opposed to :private-key) #216

Closed
sundbp opened this Issue · 6 comments

2 participants

@sundbp

When using make-user and passing a private key path, as opposed to a private key literal value, it seems something gets confused and the key doesn't get used properly.

A few snippers illustrating it:
https://www.refheap.com/paste/12911
https://www.refheap.com/paste/12912

@hugoduncan
Owner

@sundbp Is your key in the keychain (assuming this is on OS X locally)?

@sundbp

Fails either way. I use ssh-agent and ssh-add via scripts, not sure how that and if that hooks into OSX keychain thing (not a long time OSX user), use the same on linux.

@hugoduncan
Owner

OK, sounds like it's not in the OS X keychain then. Note the keychain is distinct from the ssh-agent.

@sundbp
@hugoduncan
Owner

@sundbp I'm closing this. Please reopen if it is still an issue.

@hugoduncan hugoduncan closed this
@sundbp

Cool. I started manually adding keys to via ssh-add as a principle. Think the auto-add key still is broken but haven't tried in quite a while so can't comment for sure. Either way I have a workaround.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.