mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[PR #126] [MERGED] enh: config: detect warnBefore/idleTimeout misconfiguration #258
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#258
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/126
Author: @speed47
Created: 1/19/2021
Status: ✅ Merged
Merged: 1/19/2021
Merged by: @speed47
Base:
master← Head:issue125📝 Commits (1)
fefdf05enh: config: detect warnBefore/idleTimeout misconfiguration📊 Changes
3 files changed (+17 additions, -6 deletions)
View changed files
📝
doc/sphinx/administration/bastion_conf.rst(+3 -3)📝
etc/bastion/bastion.conf.dist(+3 -3)📝
lib/perl/OVH/Bastion/configuration.inc(+11 -0)📄 Description
Before, an inconsistency in the configuration settings of the warnBefore(Lock|Kill)Seconds
and idle(Lock|Kill)Timeout could break any new connection (ttyrec refuses to launch).
Now we detect this case properly, and fallback to a sane setting for
warnBefore(Lock|Kill)Seconds (zero) if those were set without enabling the corresponding
idle(Lock|Kill)Timeout setting. We also log an error to syslog when it happens,
so that the sysadmin can fix their configuration.
Added hints about how these configuration options work together in the bastion.conf.dist file.
Fixes #125
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.