Repository navigation
End reusable sudo authorization before installers and reduce update work - #14914
thebytorsnowdog wants to merge 1 commit into
Conversation
|
|
Strong update-boundary hardening: revoke the reusable sudo timestamp before hooks / mise / AUR, stop forcing Product/UX note to flag for maintainers: AUR installs and some hooks will prompt for sudo more often than today — that’s intentional. Migration Please coordinate with other open sudo/mise boundary work (#14800, #14135) so we don’t thrash the same update path. |
|
Additional validation for the hook/mise boundary at I tested a local integration of this change and compared the relevant code with the PR head. The post-update hook/mise block, authorization and cleanup functions, and lock/stay-awake helpers match byte for byte.
These results add evidence for the shared boundary and cleanup code; they are not a test of the complete PR head. The PR’s additional AUR changes and mise release-age policy, full package transactions and interactive authentication prompts remain outside these checks. |
|
Closing this one; #16568 replaced it. The update now runs under a single sudo authorization on purpose, AUR and the boot check included, so it stops asking for the password again near the end. Thanks for digging into this! |
Updates currently keep reusable sudo authorization active through post-update hooks and mise installation, and the AUR picker also maintains that authorization during builds. End the trusted system-update session before those stages and apply the existing command-scoped sudo wrapper consistently, including direct AUR updates.
This also removes avoidable work and respects existing installation policy:
updatedbafter AUR installation; regular scheduled indexing remains responsible for refreshing locate results.MISE_MINIMUM_RELEASE_AGE=0. Preserve configured policy and explicit environment overrides; migrate only exact generated wrappers, leaving customized launchers untouched.Validation:
test/shell.d/{update-hook-security,update-user-path,update-sequence,update-disk-space,pkg-aur-sudo-boundary,update-aur-sudo-boundary,channel-sudo-boundary,security-source-root,security-entrypoint-symlink}-test.shusing the real scripts with harmless privilege/package fixtures.test/shell.d/{mise-release-age,mise-wrapper-quiet-migration,mise-install,agent-account-exec,locate,update-boot-verify,update-restart-phases,channel,pacman-templates}-test.sh. Account dispatch used real offline mise; locate exercised real indexing of a temporary tree and verified neither successful nor failed AUR builds trigger indexing.AUR installations and privileged hooks may require separate password prompts, and newly installed files may not appear in locate until scheduled indexing runs. This limits credential reuse within these workflows; it does not sandbox installer code or prevent independently authorized concurrent activity. No complete installed-OS update or clean full-suite result is claimed.