mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 16:35:33 +02:00
[GH-ISSUE #219] Question on known host keys #59
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Jul 9, 2021).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/219
In our organization we are regularly replacing instances which we access using the bastion. Due to the nature of SSH we constantly have to run the command to forget the known host key before we are allowed to connect. I know this is not really a Bastion issue by itself but I am curious to see how you as a large organization managed to get around this.
I know there is the option to make sure all instances behind the bastion share the same SSH keys, but perhaps there is an even better solution?
Feel free to close this issue if you believe it is logged in the wrong place.
@ghost commented on GitHub (Jul 9, 2021):
Should have read the documentation properly: https://ovh.github.io/the-bastion/plugins/restricted/accountModify.html#cmdoption-accountmodify-egress-strict-host-key-checking