-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-think how TMOUT is handled #23
Comments
We could add |
Value should be no more than 15 minutes. |
Related issue: #72 |
The timeout value should be a variable and used consistently across various configs. |
pyllyukko
added a commit
that referenced
this issue
Dec 29, 2021
* Relates to #23 * Now with a variable! \o/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Installing
tmout.sh
into/etc/profile.d
is necessarily not enough. E.g. ifsudo
is invoked without-i
, it doesn't apply.autologout.csh
sudoers
,sudo_env
,tmout.sh
,autologout.csh
&autolog.conf
Examples from different guides:
NSA RHEL guide
2.3.5.5 Implement Inactivity Time-out for Login Shells
/etc/profile.d/tmout.sh
:system-hardening-10.2.txt
/etc/profile
:CIS CentOS Linux 7 Benchmark v3.0.0
5.4.4 Ensure default user shell timeout is configured (Automated)
profile
/etc/bashrc
CIS Debian Linux 10 Benchmark v1.0.0
/etc/bash.bashrc
profile
The text was updated successfully, but these errors were encountered: