[GH-ISSUE #491] Feature Request: auto accept keys #127

Closed
opened 2026-05-07 00:19:16 +02:00 by BreizhHardware · 3 comments

Originally created by @tgeek77 on GitHub (Aug 9, 2024).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/491

Our use case:

We would like to use The Bastion with our automated testing environment. Our tests include creating a new VM with terraform and once it is up, we ssh in and run some tests.

We would like The Bastion to handle the ssh portion, however since a new VM is being created on every key, when we log in the first time, we get an ssh message asking us if we want to use the key (Yes/No/Fingerprint). This mandatory question breaks automation and so we have to use direct ssh instead.

It would be great to have an autoaccept function. In most cases, this would be a security risk however if you want to use The Bastion in an internal-only trusted environment, this would be a huge help with minimal risk.

Originally created by @tgeek77 on GitHub (Aug 9, 2024). Original GitHub issue: https://github.com/ovh/the-bastion/issues/491 Our use case: We would like to use The Bastion with our automated testing environment. Our tests include creating a new VM with terraform and once it is up, we ssh in and run some tests. We would like The Bastion to handle the ssh portion, however since a new VM is being created on every key, when we log in the first time, we get an ssh message asking us if we want to use the key (Yes/No/Fingerprint). This mandatory question breaks automation and so we have to use direct ssh instead. It would be great to have an autoaccept function. In most cases, this would be a security risk however if you want to use The Bastion in an internal-only trusted environment, this would be a huge help with minimal risk.
Author
Owner

@speed47 commented on GitHub (Sep 25, 2024):

This feature is already available, you can set it per-account on the bastion, the option you're looking for is accountModify --egress-strict-host-key-checking accept-new (see https://ovh.github.io/the-bastion/plugins/restricted/accountModify.html?highlight=accountmodify#cmdoption-accountModify-egress-strict-host-key-checking )

<!-- gh-comment-id:2373496454 --> @speed47 commented on GitHub (Sep 25, 2024): This feature is already available, you can set it per-account on the bastion, the option you're looking for is ``accountModify --egress-strict-host-key-checking accept-new`` (see https://ovh.github.io/the-bastion/plugins/restricted/accountModify.html?highlight=accountmodify#cmdoption-accountModify-egress-strict-host-key-checking )
Author
Owner

@tgeek77 commented on GitHub (Sep 25, 2024):

Thanks, I'll check it out.

<!-- gh-comment-id:2374412367 --> @tgeek77 commented on GitHub (Sep 25, 2024): Thanks, I'll check it out.
Author
Owner

@speed47 commented on GitHub (Oct 16, 2024):

Closing as fixed, please reopen if needed.

<!-- gh-comment-id:2416393703 --> @speed47 commented on GitHub (Oct 16, 2024): Closing as fixed, please reopen if needed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/the-bastion#127
No description provided.