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

Support for SSH #101

Open
mustafagonul opened this issue May 4, 2020 · 3 comments
Open

Support for SSH #101

mustafagonul opened this issue May 4, 2020 · 3 comments

Comments

@mustafagonul
Copy link

The ssh configuration can be as follows:

# Github
Host github.com
    User git
    HostName github.com
    IdentityFile ~/.ssh/id_rsa_gitall
    ProxyCommand socat - PROXY:<proxy>:%h:%p,proxyport=<port>

# Gitlab
Host gitlab.com
    User git
    HostName altssh.gitlab.com
    Port 443
    IdentityFile ~/.ssh/id_rsa_gitall
    ProxyCommand socat - PROXY:<proxy>:%h:%p,proxyport=<port>

I appreciate it if the can support edit/change .ssh/config file.

@himanshub16
Copy link
Owner

himanshub16 commented May 6, 2020

This seems doable, given the end-user is confident enough to make this particular change to each of their ssh config. I guess there can be cases where the config is for another machine on a private network, and connecting doesn't require proxy with SSH.

Considering this, we can have it exempted from all option and make the user run it manually when needed.
Thoughts?

@mustafagonul
Copy link
Author

I agree with you. This should be done separately from all configuration. ProxyMan should have two kinds of configuration. The first type of configurations can be included in all, the second type of configurations are not included in all configuration. The options should be listed separately so that the user can identify the difference.

Besides this topic, I would like to say something regarding the ssh. If the ssh option is selected, ProxyMan should list all the ssh configuration and the user should select which one she wants to be edited.

@mustafagonul
Copy link
Author

After some investigation, I guess the best way is to implement this feature writing a wrapper script and assigning this wrapper script into git configuration or setting the GIT_PROXY_COMMAND environment. That also means that I don't think managing ssh configurations separately is necessary.

Setting GIT_PROXY_COMMAND in bashrc and zshrc can be better.

Please check the following links:

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

No branches or pull requests

2 participants