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

Translate ssh-config rules and don't simply replicate #46

Open
caffeineflo opened this issue Dec 15, 2016 · 3 comments
Open

Translate ssh-config rules and don't simply replicate #46

caffeineflo opened this issue Dec 15, 2016 · 3 comments

Comments

@caffeineflo
Copy link

I have a couple of ssh-config rules setup, e.g.
Host * and Host name-*
I would assume that these rules would be applied to the individual hosts they correspond to at the time of sync, yet the sync simply added a new host for each of those rules to my list of hosts when synced.

Another thing that this sync issue brought is that I now have the same pem file over 100 times added as an identity as I had a rule setup using that exact pem file for a couple of hosts ...

@EvgeneOskin
Copy link
Contributor

Hi @caffeineflo.

As far as I understand, you want to translate a ssh-config rules setup into groups and hosts in termius. It seams a great idea!

But I doubt with naming such groups. I believe, the simplest solution is to use the same name as the ssh-config rules. What do you think?

@aaronSkar
Copy link

aaronSkar commented Dec 28, 2016

Not to hijack this or anything but I would like to bring hosts into groups as well as pre-save the identity to be used. Is there a syntax for this? Importing from Linux .ssh/config. The identity things is minor compared to importing to the proper groups (I have hundreds of sessions). Maybe something like:

Host my-host-name
 	  Hostname some-ip-address
 	  Port 22
 	  identity my-saved-identity
 	  group_name my-saved-group-name

@lejmr
Copy link

lejmr commented Jun 26, 2018

That bugs me as well. I have already implemented grouping through comment tag in #125 and I want to implement these wildcard hosts as well. I use wildcard hosts quite extensively.

I am going to extract all wildcard host's configuration options into group options. If there is a group tag attached to this wildcard hosts, I will translate the group tag into group name which gets configuration options of this wilcard host.. Otherwise, I will try to come up with same neat naming convention derived from the wildcard name :-)

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

No branches or pull requests

4 participants