-
Notifications
You must be signed in to change notification settings - Fork 18
Customizing the ssh command #49
Comments
There is an option for setting the binary used, though it's slightly hackish: set the PUSHY_NATIVE_SSH environment variable to "gsissh". As long as you do this before importing pushy, you're set. See: https://github.com/pushyrpc/pushy/blob/master/pushy/transport/ssh.py#L139 There's not currently a way of passing arbitrary arguments through. What do you need to pass? Is it static? If so, then you could create a wrapper for gsissh that passes those arguments. Otherwise, I'd be okay with a pull request to support passing through non-standard arguments. I should inform you that I am not actively working on the project, and I do not have much time for it. Please bear this in mind as you consider migrating your existing tools. |
Ah... the PUSHY_NATIVE_SSH is almost what I want. The only problem is that you require it to be a single file; E.g., something along the lines of Any chance you could allow this? Thanks, PS: Having an explicit setting for this would be even better. |
That sounds reasonable. I'm thinking something like this: pushy.transport.ssh.set_native(["gsissh", "-S", mycache_fname]) which will raise an exception if "gsissh" doesn't exist, and otherwise tell the SSH transport to use the arguments provided. |
Yep, that would be great. BTW: Please do the same for scp. Thanks, PS: I assume you will post on this thread once it is done. |
One further comment: Looks like now it expects the abspath:
[0905] sfiligoi@engage-submit-1 ~$ which gsissh |
Sure, however, as I mentioned earlier, I do not have much time for Pushy. I don't know when I'll get to this. If you would like it soon(er), I suggest you make the changes and send a pull request (or just maintain a fork). |
OK, will do the changes and let you know. Spending time coding is not a problem, but do not want to maintain a fork. Thanks, On 11/25/2013 04:54 PM, Andrew Wilkins wrote:
|
We are currently using ssh through a set of custom wrappers, and are considering moving to pushy.
However, we also want to be able to customize the ssh command that is being used.
Both in terms of arguments being passed and the actual binary name (we use gsissh).
I currently cannot find any way to customize this is pushy.
Is there a way? Would you be willing to consider adding the option, else?
Thanks,
Igor
The text was updated successfully, but these errors were encountered: