Shrink fast-shutdown, gpg, increase-file-watchers, increase-lockout-limit to runtime-only ops
Each script's static-file write moves to omarchy-settings. The scripts keep only the runtime side: reload systemd, restart dirmngr, sysctl --system, or (for lockout-limit) the PAM seds that have to stay scripted because /etc/pam.d/system-auth and /etc/pam.d/sddm-autologin are upstream-owned and need targeted line edits rather than a full-file override. faillock.conf's deny=10 (formerly inside increase-sudo-tries.sh sed) now rides through the etc-overrides dance in omarchy-settings.
This commit is contained in:
@@ -1,3 +1,8 @@
|
||||
# The faillock.conf side ships via the omarchy-settings etc-overrides
|
||||
# (deny = 10). The two PAM file edits below remain a script because
|
||||
# /etc/pam.d/system-auth and /etc/pam.d/sddm-autologin are upstream-owned
|
||||
# and the changes are insertions, not full-file overrides.
|
||||
|
||||
# Increase lockout limit to 10 and decrease timeout to 2 minutes
|
||||
sudo sed -i 's|^\(auth\s\+required\s\+pam_faillock.so\)\s\+preauth.*$|\1 preauth silent deny=10 unlock_time=120|' "/etc/pam.d/system-auth"
|
||||
sudo sed -i 's|^\(auth\s\+\[default=die\]\s\+pam_faillock.so\)\s\+authfail.*$|\1 authfail deny=10 unlock_time=120|' "/etc/pam.d/system-auth"
|
||||
|
||||
Reference in New Issue
Block a user