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

util/ssh: Enable StrictHostKeyChecking SSH option #1549

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

onurcelep
Copy link

Description
Enables setting StrictHostKeyChecking option for SSH client by introducing LG_SSH_STRICT_HOST_KEY_CHECKING environment variable.

Checklist

  • Documentation for the feature
  • Tests for the feature
  • The arguments and description in doc/configuration.rst have been updated
  • Add a section on how to use the feature to doc/usage.rst
  • Add a section on how to use the feature to doc/development.rst
  • PR has been tested
  • Man pages have been regenerated

@jluebbe
Copy link
Member

jluebbe commented Nov 21, 2024

StrictHostKeyChecking is already enabled for connections to exporters. Why would you want to disable that?

Enables setting StrictHostKeyChecking option for SSH
client by introducing LG_SSH_STRICT_HOST_KEY_CHECKING
environment variable.

Signed-off-by: Onur Celep <[email protected]>
@onurcelep
Copy link
Author

onurcelep commented Nov 21, 2024

StrictHostKeyChecking is already enabled for connections to exporters. Why would you want to disable that?

by "Enable" I mean being able to modify it :) In my setup exporter runs on a gateway device paired (1-on-1) with device under test (there is an isolated network between), coordinator also hosted on a separate server. When I try to reach video stream through dockerized exporter it throws strictHostKeyChecking error for exporter host, meaning I would need to add exporter hosts for each pair to my ssh config.

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

Successfully merging this pull request may close these issues.

2 participants