Date: Wed, 16 Oct 2024 15:42:25 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282005] security/gnome-keyring - the race between pam_gnome_keyring and pam_xdg or something else prevents it from loading keys on login Message-ID: <bug-282005-227-UZD3bPL5fW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282005-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282005 --- Comment #3 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- This port builds fine without the patch[1]. Removing this patch doesn't fix the described issue though. The keyring pam module still expects the old directory[2] to create the trusted file. Maybe the FreeBSD Foundation can sponsor resolving this issue by making the pam_xdg path more configurable. It's strictly bound with the recently announced expansion into the laptop user base. 1. https://cgit.freebsd.org/ports/tree/security/gnome-keyring/files/patch-pam_gkr-pam-client.c 2. Oct 16 17:20:42 fomalhaut gnome-keyring-daemon[4885]: couldn't access control socket: /var/run/user/1001/keyring/control: No such file or directory -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282005-227-UZD3bPL5fW>