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.

Sign up for GitHub

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

Jump to bottom

Using OpenSSH to connect to leaf agentless nodes results in hostkey warning #25511

Open
capnspacehook opened this issue May 2, 2023 · 0 comments
Open

Using OpenSSH to connect to leaf agentless nodes results in hostkey warning #25511

capnspacehook opened this issue May 2, 2023 · 0 comments
Assignees
@capnspacehook
Labels
agentless bug test-plan-problem Issues which have been surfaced by running the manual release test plan

Comments

@capnspacehook
Copy link
Contributor

Expected behavior:

Connecting to leaf agentless nodes using OpenSSH ssh client configured correctly with a Teleport cluster will never show a hostkey warning

Current behavior:

When using the cluster suffix (hostname.cluster) as recommended in the docs, ssh sees a new host key every time. If the cluster suffix is not used, ssh doesn't complain and therefore likely sees the same host key/a host key signed by the same trusted CA.

Bug details:

  • Teleport version: v13, on commit e280dfc
  • Recreation steps: see above
@capnspacehook capnspacehook added bug test-plan-problem Issues which have been surfaced by running the manual release test plan agentless labels May 2, 2023
@capnspacehook capnspacehook mentioned this issue May 2, 2023
Closed
@capnspacehook capnspacehook self-assigned this May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@capnspacehook capnspacehook

Labels
agentless bug test-plan-problem Issues which have been surfaced by running the manual release test plan
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@capnspacehook