On Tue, 28 May 2024 at 14:45, Luca Boccassi <bl...@debian.org> wrote: > > On Tue, 28 May 2024 at 14:19, Luca Boccassi <bl...@debian.org> wrote: > > > > On Tue, 28 May 2024 at 14:18, Anthony Bourguignon <debian+...@toniob.net> > > wrote: > > > > > > Le mardi 28 mai 2024 à 14:06 +0100, Luca Boccassi a écrit : > > > > On Tue, 28 May 2024 at 14:05, Anthony Bourguignon > > > > <debian+...@toniob.net> wrote: > > > > > > > > > > Le mardi 28 mai 2024 à 12:38 +0100, Luca Boccassi a écrit : > > > > > > On Tue, 28 May 2024 13:09:53 +0200 Anthony Bourguignon > > > > > > <debian+...@toniob.net> wrote: > > > > > > > Hi, > > > > > > > > > > > > > > Since 256~rc3-3, I can’t login anymore with my homed user. How it > > > > > > > happened : I logged in with GDM to > > > > > > > my Gnome session. I made the updates, including the systemd-homed > > > > > > > version 256~rc3-3. When I locked > > > > > > > my screen, I was unable to unlock it. The password was refused. > > > > > > > So I > > > > > > > restarted the computer and I > > > > > > > was unable to log back onto it. > > > > > > > > > > > > > > I tried with Gnome, ssh, su (as root), nothing worked. > > > > > > > > > > > > > > I think your modifications completely broke systemd-homed > > > > > > > authentification. The system didn’t > > > > > > > recognize the user at all : > > > > > > > 2024-05-28T11:42:29.266019+02:00 **redacted** unix_chkpwd[2223]: > > > > > > > check pass; user unknown > > > > > > > 2024-05-28T11:44:17.113169+02:00 **redacted** unix_chkpwd[2351]: > > > > > > > could not obtain user info > > > > > > > (**redacted**) > > > > > > > > > > > > > > I rsynced the /etc/pam.d/common* files from another computer, > > > > > > > deleted > > > > > > > the systemd-homed file in the > > > > > > > same directory, and everything is back to normal. > > > > > > > > > > > > uff I tested it from a TTY rather than GNOME and it worked. Does it > > > > > > work from the console for you? > > > > > > > > > > > > > > > > I’ve tried with another PC. From the console, I can log in but the > > > > > session closes directly. If, > > > > > from > > > > > root, I try "su - username", I’ve got the message : "called without > > > > > reference on home taken, > > > > > can’t > > > > > operate" and the session doesn’t open. > > > > > > > > > > If I try to log in Gnome from GDM, it works, but it seems the home > > > > > directory is not uncrypted > > > > > and > > > > > mounted. So my session is clear and I can’t launch any app. > > > > > > > > > > But I don’t understand why I don’t have the same behavior as the > > > > > other PC. > > > > > > > > Ok, activation of the homed entry was borked then - what's the > > > > situation in your /etc/pam.d? Do you still have systemd_home > > > > references outside of its own config module? > > > > > > The only references to systemd_home are in /etc/pam.d/systemd-homed . > > > Nothing in the common* files. > > > > Ok - I'll try to reproduce later tonight > > In the meanwhile, if you are feeling adventurous and want to mess with > the pam config, if you find a way to make it happy let me know
256~rc3-5 should fix it - turns out standalone modules cannot work in Debian, so it's back to pam-auth-update + monkey patching
