David Heinemeier HanssonandClaude Opus 5
536fcd5c6c
setup is where a user goes to configure something: direct boot, security keys, hibernation. These three are not that. omarchy-apply-system is the ISO's entry point in the target chroot, omarchy-apply-hardware is what it calls for device quirks, and omarchy-apply-lock is called by install/config/lockscreen-pam.sh. apply is the verb they already used to describe themselves, and it carries the contract: declared state under install/ converged onto the machine, idempotent, safe to repeat. The group gets no GROUP_DESCRIPTIONS entry on purpose. That table drives the top-level group list on its own, so an entry would put apply back in front of users even with every command in it hidden, the way provision already stays out. A test covers it. The ISO installs the runtime from the mirror it ships with, so it moves to the new names in lockstep and no compatibility route is needed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
54 lines
1.8 KiB
Bash
Executable File
54 lines
1.8 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Configure Quickshell lock screen authentication
|
|
# omarchy:requires-sudo=true
|
|
# omarchy:hidden=true
|
|
|
|
set -e
|
|
|
|
target_user=${OMARCHY_INSTALL_USER:-${SUDO_USER:-}}
|
|
if [[ -z $target_user && -n ${PKEXEC_UID:-} ]]; then
|
|
target_user=$(getent passwd "$PKEXEC_UID" | cut -d: -f1)
|
|
fi
|
|
target_user=${target_user:-$USER}
|
|
|
|
as_root() {
|
|
if (( EUID == 0 )); then
|
|
"$@"
|
|
else
|
|
sudo "$@"
|
|
fi
|
|
}
|
|
|
|
echo "Configuring lock screen password authentication..."
|
|
|
|
as_root tee /etc/pam.d/omarchy-lock-password >/dev/null <<'EOF'
|
|
#%PAM-1.0
|
|
auth required pam_faillock.so preauth silent deny=10 unlock_time=120
|
|
-auth [success=2 default=ignore] pam_systemd_home.so
|
|
auth [success=1 default=bad] pam_unix.so try_first_pass nullok
|
|
auth [default=die] pam_faillock.so authfail deny=10 unlock_time=120
|
|
auth optional pam_permit.so
|
|
auth required pam_env.so
|
|
auth required pam_faillock.so authsucc
|
|
account include system-local-login
|
|
EOF
|
|
|
|
if omarchy-cmd-present fprintd-list && fprintd-list "$target_user" 2>/dev/null | grep -qi finger; then
|
|
echo "Configuring lock screen fingerprint authentication..."
|
|
as_root tee /etc/pam.d/omarchy-lock-fingerprint >/dev/null <<'EOF'
|
|
#%PAM-1.0
|
|
auth required pam_fprintd.so
|
|
account include system-local-login
|
|
EOF
|
|
else
|
|
as_root rm -f /etc/pam.d/omarchy-lock-fingerprint
|
|
fi
|
|
|
|
# omarchy-shell can't reach a running shell during chroot install. The echo
|
|
# is just confirmation, so swallow the failure rather than letting it become
|
|
# the script's exit code.
|
|
if omarchy-shell lock status >/dev/null 2>&1; then
|
|
echo "Lock screen authentication configured."
|
|
fi
|