docs(pam): correct the lock-policy test procedure against a real run - #2
Merged
Conversation
Four commands in the procedure were wrong when actually run on this machine: - pamtester is in the AUR, not the official repos, so `pacman -S` fails. - Ctrl+Alt+F2 is sddm here; the free TTY for the root shell is F3. - Bare `faillock --reset` also tries root's tally and errors on it. - `hyprctl dispatch exec hypridle` is rejected by the Lua config, which parses the dispatch argument as Lua. Also records the expected output of a green run, the pacman -Qkk fallback for when the before-snapshot was never taken, and the two log lines that look like faults but are not — pamtester's unprivileged audit-write failure, and pam_unix not logging successful auths at all.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1. Running the bhdai/quickshell_config#64 acceptance gate for real
exposed four commands in the procedure that don't work on this machine:
sudo pacman -S --needed pamtesteryay -S --needed pamtester— it's AURCtrl+Alt+F2for the root shellCtrl+Alt+F3— F2 is sddm herefaillock --resetfaillock --user $USER --reset— the bare form also tries root's tally and errorshyprctl dispatch exec hypridlesetsid hypridle >/dev/null 2>&1 &— the Lua config parses the dispatch arg as LuaAlso adds three things the run taught us:
pacman -Qkk pambase sudo util-linuxas the after-the-fact check on the sharedstacks, for when the before-snapshot was never taken. It's stricter than the
snapshot — it compares against the package database rather than your own earlier copy.
Error sending audit message, and the fact thatpam_unixlogs no successfulauths at all, so a clean run leaves no positive trace.