Repository navigation
feat!: the password says who you are, one LUKS slot per account - #7
Merged
Merged
Conversation
From Omarchy PRs #16100 and #16920, and the session-switching findings posted there. SDDM 0.21 starts a new greeter on the first console, which fails while an automatic login's desktop holds it and leaves the screen dark. Switch user now waits for that console, and goes back to a login screen already running instead of asking for a second one. A password or fingerprint accepted once the session is in the background no longer opens it, and a session in the background doesn't take the fingerprint reader back on resume. System > Switch User (omarchy-mu-user-switch) does the same from an open desktop. Also: Setup > Users' entries stay out of the search of users outside wheel, omarchy-mu-user-add refuses while /etc/sddm.conf logs someone in automatically, omarchy-mu-user-remove stops when the account's disk password can't be removed, a password chosen at the first login has at least 6 characters, and SDDM has ReuseSession=true set here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replaces the list of users on the login screen with the model of Omarchy PR #16920. Each account's password is also its own LUKS key slot, recorded in /etc/omarchy-multiuser/slots, with at least 6 characters and nobody else's. The boot image notes which slot opened the disk (omarchy-mu-luks-slot), and omarchy-mu-login-select logs that person in, once. Anything unsure shows the login screen, which is now a password box that finds the account (omarchy-mu-login-match). omarchy-mu-user-password changes a password everywhere at once, journaled, through omarchy-mu-user-helper. This is a separate commit so it can be reverted alone: it adds a wrapper to the initramfs, which could stop the disk from opening if it is wrong, and it has not run on a real boot, PAM stack or SDDM yet. Gone: the user list, Other user..., choosing a password at the first login, omarchy-mu-luks-enroll, omarchy-mu-accounts first-login, and omarchy-mu-user-add's --luks and --set-password. Every person has to run omarchy-mu-user-password after upgrading; the warning for that needs the next release to be 0.10.0 or later. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…atic login Removing an account, or logging it out when taking its rights, ended a desktop opened by the disk prompt by force. SDDM takes that for a crash and shows nothing more on the first console, so the machine stayed dark there. It is now asked for its login screen, which takes over the screen, and the person at another console is told how to come back. Putting them back at once left the greeter dark for good, since its compositor had lost the console before setting up the display. Going to another console and back also left the greeter without the keyboard until a click, as Qt drops the field's focus. It now takes the focus back. Found running both on a real install in a VM. Also corrects the README on what a key does on a dark lock screen, and marks two intended patterns for shellcheck. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The guard watches /etc/sddm.conf.d, so the cleanup in pre_remove ran it, and it put back the omarchy-mu-login-match line in /etc/pam.d/sddm, naming a script about to be gone. The path units now go off before anything else is cleaned up. Found rehearsing the rollback in a VM. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ackage pre_remove didn't disable omarchy-mu-migrate-record@<admin>.path, so each one's link in multi-user.target.wants stayed, dangling, once the unit file was gone. They are now disabled, and a link systemctl can't disable is deleted. Found rehearsing the rollback in a VM, and checked there with a real removal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
Replaces the list of users on the login screen with the model of Omarchy PR omacom/omarchy#16920: each account's password is also its own LUKS key slot, and the password alone says who is logging in. Also brings in what was useful from omacom/omarchy#16100 and from the session-switching findings posted on both.
What changes
omarchy-mu-luks-slot), andomarchy-mu-login-selectopens that person's desktop, once. With one account on an encrypted disk, it is logged in. Anything unsure shows the login screen.omarchy-mu-login-match, first in SDDM's PAM auth stack). The user list, Other user… and choosing a password at the first login are gone.omarchy-mu-user-passwordchanges one everywhere at once, journaled. Each has at least 6 characters and is nobody else's.Breaking
omarchy-mu-user-passwordafter upgrading. The warning for that only fires when upgrading to 0.10.0 or later, so the next release has to be at least 0.10.0.PKGBUILDis still at 0.9.0: this PR doesn't do the release.omarchy-mu-user-addloses--luksand--set-password.omarchy-mu-luks-enrollandomarchy-mu-accounts first-loginare gone.Review with care
afa158aadds a wrapper aroundcryptsetupto the initramfs. A mistake there could stop the disk from opening, so it is a separate commit that can be reverted alone. Its message says it had not run on a real boot yet; the testing below came after it.omarchy-mu-login-matchreads passwords inside SDDM's PAM stack. An owner with failed logins on record deliberately gets the slow refusal, so a fast one doesn't reveal a lockout.Testing
96dbe78, whose fix was only checked in the VM.Not yet tested on real hardware:
Known and left alone
omarchy-mu-login-match failed: exit code 1, becausepam_execreports that script's "carry on" answer as an error. Cosmetic.🤖 Generated with Claude Code