mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[PR #420] [CLOSED] Implement Ingress Secure Keys #467
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#467
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/420
Author: @P-EB
Created: 9/25/2023
Status: ❌ Closed
Base:
master← Head:master📝 Commits (4)
54d12c7Implement Ingress Secure Keys5af7e55Escape dots in regex patterns for ssh algorithmsb9b4899Factor out in a generic function the helper listing allowed ssh key algorithm72be788Drop an unused variable in print_accepted_key_algorithms📊 Changes
6 files changed (+38 additions, -34 deletions)
View changed files
📝
bin/plugin/open/selfAddIngressKey(+1 -14)📝
bin/plugin/restricted/accountCreate(+1 -13)📝
etc/bastion/bastion.conf.dist(+1 -1)📝
lib/perl/OVH/Bastion.pm(+1 -1)📝
lib/perl/OVH/Bastion/configuration.inc(+2 -2)📝
lib/perl/OVH/Bastion/ssh.inc(+32 -3)📄 Description
This is a draft lacking unit/functional tests.
I'd like to get your feeling about including SecureKeys.
Regarding testing, I'd be happy to write the tests but I'm not sure to have understood the code flow and style in
330-selfkeys.sh.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.