From 4d0e4f1266d6aeed4d0bfea43781fefe06e6f923 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Fri, 16 Oct 2026 09:38:38 +0200 Subject: docs(spec): user details leaves the password out passwd in a terminal already does it, AccountsService's SetPassword needs admin rights and a hash, and a change desyncs the login keyring. Co-Authored-By: Claude Opus 5.5 --- docs/superpowers/specs/2026-10-16-user-details-design.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/superpowers/specs/2026-10-16-user-details-design.md') diff --git a/docs/superpowers/specs/2026-10-16-user-details-design.md b/docs/superpowers/specs/2026-10-16-user-details-design.md index 2b2819b..93aa170 100644 --- a/docs/superpowers/specs/2026-10-16-user-details-design.md +++ b/docs/superpowers/specs/2026-10-16-user-details-design.md @@ -93,5 +93,9 @@ AccountsService or touches the real git config. - Values are read on open; a change made elsewhere while the page is open is not seen until it reopens. - No `~/.face.icon`: SDDM reads the AccountsService icon. +- No password. `passwd` in a terminal already does it safely, and + AccountsService's `SetPassword` needs admin rights and a pre-hashed value. + Changing it also leaves the gnome-keyring unlocked at login on the old + password, since the `passwd` PAM stack does not re-key it. - No vCard, no social links, no GPG key: nothing on the desktop reads them. The field list is where they would go. -- cgit v1.2.3