-
Notifications
You must be signed in to change notification settings - Fork 45
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
Could not parse valid .ssh/config #51
Comments
Given the SSH settings are already configured through SSH config, it would be enough to just read the At least that's what the SSH Search Provider Extension (https://github.com/brot/gnome-shell-extension-sshsearch) does. |
Fixed .ssh/config parsing but replaces it by a simpler algorithm, ignoring HostName, User, Port (and IdentityFile, which is already ignored)
Fixed .ssh/config parsing but replaces it by a simpler algorithm, ignoring HostName, User, Port (and IdentityFile, which is already ignored)
Bump, Any update of this issue. I'm trying to use this feature, but I canot get ConnectionManager to load my config. |
Fixed .ssh/config parsing but replaces it by a simpler algorithm, ignoring HostName, User, Port (and IdentityFile, which is already ignored)
Fixed .ssh/config parsing but replaces it by a simpler algorithm, ignoring HostName, User, Port (and IdentityFile, which is already ignored)
My .ssh/config looks like this:
However, ConnectionManager is not able to parse it. I did a look into the code, and there are a couple of problems here:
Host example.com example.org
is not translated into two entries, but only oneHostName
entry, the previous entry is reused.All in all this results into
example.com example.org
containingme@[email protected]
Expected behavior would be:
Host
by \s+ and create entry for each of resulting itemsHostName
is not set, use value ofHost
(that is the current item) insteadGiven the above example, the following result is expected:
example.de
:[email protected]
example.com
:[email protected]
example.org
:[email protected]
The text was updated successfully, but these errors were encountered: