-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Fix host ordering in .ssh/config output #205
Comments
@moul any pointers on this, this is biting my quite badly (but for |
This is the biggest drawback of assh. 😞 Instead of preserving the origin order, assh sorts the new config by alphanumeric. With regular ssh, the order is extremely important, as it can allow for wildcards+overridable variables, i.e.: hosts:
stg-bastion:
User: bumblebee
IdentityFile: ~/.ssh/acme/bumblebee
"stg-*":
User: optimus
IdentityFile: ~/.ssh/acme/staging With regular ssh, @moul Even tweaking the sorting algorithm to order For example (sorting
Unfortunately now
Any intention of solving this wildcards+overrides situation? |
What is the status here? I have the same problem |
Breaking out from #190.
Example ssh config:
ssh uses the first value found for each setting. This config will use the
regular
key for all *.bar servers but use thespecial
key for all foo*.bar servers. But if I create the same config in assh:This generates the following config file:
The ordering has been reversed! This will use the wrong key file for foo servers.
The text was updated successfully, but these errors were encountered: