search

yanne / api-test

0 stars 0 forks source link

Make the path to .ssh configurable in the Library #35

Closed yanne closed 10 years ago

yanne commented 10 years ago

It should be available both at loadtime and runtime.

This issue was originally opened at Google Code on Sep 21, 2011.

yanne commented 10 years ago

Original comment by pekka.klarck on Sep 22, 2011.

What do you mean with .ssh? The configuration directory or something else? How would it affect the library behavior?

yanne commented 10 years ago

Original comment by john.gl...@gmail.com on Sep 22, 2011.

I haven't looked at the library so I don't know where it looks for the ssh keys. I'm assuming looks from the executable directory

On Unix/OSX, there is a default for where the ssh keys are kept. They are in a .ssh in /home/user so if it looked for the keys in ~/.ssh it would work most of the time. But really, this should be configurable so you don't have to copy your ssh keys into your execution path. If you're doing like I am an attempting to create a preinstalled virtualenv, that means my ssh keys are going to either have to get checked in or copied over after checkout.

On Thu, Sep 22, 2011 at 12:18 PM, robotframework-sshlibrary@googlecode.comwrote:

yanne commented 10 years ago

Original comment by john.gl...@gmail.com on Sep 23, 2011.

You can close this. Somehow I missed that the Login With Public Key keyword already does this

yanne commented 10 years ago

Original comment by janne.t....@gmail.com on Sep 25, 2011.

Seems that the original problem was not a problem after all.