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

[BUG] - SSH config files with Include sections are not supported. #309

Open
gvoysey opened this issue Nov 1, 2024 · 5 comments
Open

[BUG] - SSH config files with Include sections are not supported. #309

gvoysey opened this issue Nov 1, 2024 · 5 comments
Assignees
Labels
backlog Implementation/fix not planned yet bug Something isn't working
Milestone

Comments

@gvoysey
Copy link

gvoysey commented Nov 1, 2024

Description

Reading Host specifications from a ssh config file does not support files that use the Include directive. termscp host-name fails to connect.

Steps to reproduce

I have my ~/.ssh/config file as follows:

Include config-work
Include config-personal

and inside config-work i have a properly credentialed host:

Host foo
  HostName foo.work.com
  IdentityFile ~/.ssh/foo-key
  User work-user

If i termscp foo, i am prompted to enter the (nonexistent) password for foo (the Host).

If i move the host declaration into the ~/.ssh/config file instead of an Include-d one, I connect to the host as expected.

Expected behaviour

I expect termscp foo to work with a ssh config file that partitions Hosts by Include-d files.

Environment

@gvoysey gvoysey added the bug Something isn't working label Nov 1, 2024
Copy link

github-actions bot commented Dec 2, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale issue closed due to inactivity label Dec 2, 2024
@gvoysey
Copy link
Author

gvoysey commented Dec 2, 2024 via email

@github-actions github-actions bot removed the stale issue closed due to inactivity label Dec 3, 2024
Copy link

github-actions bot commented Jan 3, 2025

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale issue closed due to inactivity label Jan 3, 2025
@gvoysey
Copy link
Author

gvoysey commented Jan 3, 2025 via email

@github-actions github-actions bot removed the stale issue closed due to inactivity label Jan 4, 2025
@veeso veeso added the backlog Implementation/fix not planned yet label Jan 5, 2025
@veeso veeso added this to the 0.17.0 milestone Jan 5, 2025
@veeso
Copy link
Owner

veeso commented Jan 5, 2025

I need to implement it in ssh2-config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Implementation/fix not planned yet bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants