mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[PR #593] feat: add try-personal-keys option for groups #598
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#598
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?
📋 Pull Request Information
Original PR: https://github.com/ovh/the-bastion/pull/593
Author: @jon4hz
Created: 10/1/2025
Status: 🔄 Open
Base:
master← Head:feat-group-use-personal-keys📝 Commits (2)
b6e7dfdfeat: add try-personal-keys policy for groups9b8baf1fix: return booleans as 1 and 0 in the api📊 Changes
7 files changed (+181 additions, -6 deletions)
View changed files
📝
bin/helper/osh-groupModify(+28 -3)📝
bin/plugin/group-owner/groupModify(+16 -2)📝
bin/plugin/open/groupInfo(+16 -0)📝
bin/shell/connect.pl(+2 -1)📝
lib/perl/OVH/Bastion.pm(+1 -0)📝
lib/perl/OVH/Bastion/allowdeny.inc(+36 -0)📝
tests/functional/tests.d/350-groups.sh(+82 -0)📄 Description
Hi again,
I don't want to spam you with pull requests, but I've had quite some time to work on The Bastion.
With this PR, I've implemented the discussed
--try-personal-keysfeature from #585.If a group enables this policy using
groupModify --group mygroup --try-personal-keys yes, all connection attempts to servers from this group will try the user's personal ssh keys as well as the ones from the group.The policy will also apply to guest accesses.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.