mirror of
https://github.com/Kicksecure/security-misc.git
synced 2025-04-29 09:36:14 -04:00
pam-info refactoring
This commit is contained in:
parent
487f63bb01
commit
caf0099064
@ -24,6 +24,23 @@ set -o pipefail
|
|||||||
## Debugging.
|
## Debugging.
|
||||||
who_ami="$(whoami)"
|
who_ami="$(whoami)"
|
||||||
|
|
||||||
|
if [ ! "$(id -u)" = "0" ]; then
|
||||||
|
## as user "user"
|
||||||
|
## /usr/sbin/faillock -u user
|
||||||
|
## faillock: Error opening /var/log/tallylog for update: Permission denied
|
||||||
|
## /usr/sbin/faillock: Authentication error
|
||||||
|
##
|
||||||
|
## xscreensaver runs as user "user", therefore pam_faillock cannot function.
|
||||||
|
## xscreensaver has its own failed login counter.
|
||||||
|
##
|
||||||
|
## https://askubuntu.com/questions/983183/how-lock-the-unlock-screen-after-wrong-password-attempts
|
||||||
|
##
|
||||||
|
## https://www.whonix.org/pipermail/whonix-devel/2019-September/001439.html
|
||||||
|
## TODO: echo -> true
|
||||||
|
echo "$0: not started as root, exiting."
|
||||||
|
exit 0
|
||||||
|
fi
|
||||||
|
|
||||||
grep_result="$(grep "accessfile=/etc/security/access-security-misc.conf" /etc/pam.d/common-account 2>/dev/null)"
|
grep_result="$(grep "accessfile=/etc/security/access-security-misc.conf" /etc/pam.d/common-account 2>/dev/null)"
|
||||||
|
|
||||||
## Check if grep matched something.
|
## Check if grep matched something.
|
||||||
@ -62,23 +79,6 @@ fi
|
|||||||
|
|
||||||
## https://forums.whonix.org/t/how-strong-do-linux-user-account-passwords-have-to-be-when-using-full-disk-encryption-fde-too/7698
|
## https://forums.whonix.org/t/how-strong-do-linux-user-account-passwords-have-to-be-when-using-full-disk-encryption-fde-too/7698
|
||||||
|
|
||||||
if [ ! "$(id -u)" = "0" ]; then
|
|
||||||
## as user "user"
|
|
||||||
## /usr/sbin/faillock -u user
|
|
||||||
## faillock: Error opening /var/log/tallylog for update: Permission denied
|
|
||||||
## /usr/sbin/faillock: Authentication error
|
|
||||||
##
|
|
||||||
## xscreensaver runs as user "user", therefore pam_faillock cannot function.
|
|
||||||
## xscreensaver has its own failed login counter.
|
|
||||||
##
|
|
||||||
## https://askubuntu.com/questions/983183/how-lock-the-unlock-screen-after-wrong-password-attempts
|
|
||||||
##
|
|
||||||
## https://www.whonix.org/pipermail/whonix-devel/2019-September/001439.html
|
|
||||||
## TODO: echo -> true
|
|
||||||
echo "$0: not started as root, exiting."
|
|
||||||
exit 0
|
|
||||||
fi
|
|
||||||
|
|
||||||
## Does not work (yet) for login, pam_securetty runs before and aborts.
|
## Does not work (yet) for login, pam_securetty runs before and aborts.
|
||||||
## Also this should only run for login since securetty covers only login.
|
## Also this should only run for login since securetty covers only login.
|
||||||
# if [ "$PAM_USER" = "root" ]; then
|
# if [ "$PAM_USER" = "root" ]; then
|
||||||
|
Loading…
x
Reference in New Issue
Block a user