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

SSH Config HostName is ignored if the key is spelled as "hostname" or "Hostname" #10129

Closed
xhiroga opened this issue Dec 29, 2024 · 0 comments · Fixed by #10130
Closed

SSH Config HostName is ignored if the key is spelled as "hostname" or "Hostname" #10129

xhiroga opened this issue Dec 29, 2024 · 0 comments · Fixed by #10130
Labels

Comments

@xhiroga
Copy link
Contributor

xhiroga commented Dec 29, 2024

Describe the problem:
When using an SSH configuration file, Tabby does not read the HostName directive if it is spelled as hostname (all lowercase) or Hostname (capital "H"). It seems that Tabby only recognizes HostName exactly with the capital "N" and ignores other variations.

To Reproduce:

  1. Create or edit your ~/.ssh/config file.
  2. Define a host with hostname or Hostname (different cases) instead of HostName.
  3. Attempt to connect using Tabby.
  4. Tabby does not show the host.

Expected behavior:
Tabby should recognize HostName in any case variation, especially since SSH itself accepts HostName in multiple letter cases.

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

Successfully merging a pull request may close this issue.

1 participant