https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290882
--- Comment #3 from Mark Felder <[email protected]> --- You can override the path to the socket with a sddm pam configuration change like so: auth optional pam_kwallet5.so socketPath=/tmp when I do this, a socket exists! I can see /tmp/kwallet5_feld.socket is there but the auto unlocking is still not working.... I modified /usr/local/lib/libexec/pam_kwallet_init to dump the envs and also rollback to the upstream method of passing the secrets through socat instead of nc: env | /usr/local/bin/socat STDIN UNIX-CONNECT:$PAM_KWALLET5_LOGIN the dumped ENVs show PAM_KWALLET5_LOGIN=/tmp/kwallet5_feld.socket so that part is working correctly, it's just unclear why it doesn't work now when the pieces appear to be in place -- You are receiving this mail because: You are the assignee for the bug.
