Synapse SSH plugin not properly reading ~/.ssh/config
Bug #755084 reported by
Zach McCullough
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Synapse |
Fix Released
|
Undecided
|
Alberto Aldegheri | ||
Bug Description
The ssh plugin is very particular of the formatting of the config file, it does not read mine. It should not matter the amount of tabs/spaces between keys and values.
Related branches
| Changed in synapse-project: | |
| milestone: | none → 0.2.8 |
| Changed in synapse-project: | |
| status: | New → Confirmed |
Revision history for this message
| Gert van Dijk (gertvdijk) wrote | #1 |
Revision history for this message
| Alberto Aldegheri (albyrock87) wrote | #2 |
| Changed in synapse-project: | |
| assignee: | nobody → Alberto (albyrock87) |
| status: | Confirmed → Fix Committed |
| Changed in synapse-project: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I found that Synapse is case sensitive for the "Host myhost" lines. My SSH client (OpenSSH) is not case sensitive and works with all lowercase directives like "host myhost". Quoting the 'ssh_config' manpage shows that Synapse is wrong here:
"The possible keywords and their meanings are as follows (note that keywords are case-insensitive and arguments are case-sensitive):"
So I think the behaviour of Synapse should change to case-insensitive for all keywords it reads from the SSH client's configuration file.