Date: Wed, 14 Dec 2022 07:04:05 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 268033] x11/xscreensaver: Crashing and dumping core on unlock Message-ID: <bug-268033-7788-dhZpGqxqEK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268033-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-268033-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268033 Fernando Apestegu=C3=ADa <fernape@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |des@FreeBSD.org Flags|maintainer-feedback?(x11@Fr |maintainer-feedback?(des@Fr |eeBSD.org) |eeBSD.org) --- Comment #7 from Fernando Apestegu=C3=ADa <fernape@FreeBSD.org> --- (In reply to Duncan Bayne from comment #6) There is only one strlen() call in pam_exec.c: rc =3D pam_get_authtok(pamh, PAM_AUTHTOK, &authtok, NULL); if (rc =3D=3D PAM_SUCCESS) { /* We include the trailing NUL-terminator. */ authtok_size =3D strlen(authtok) + 1; Since strlen(3) segfaults if the argument is null, I guess pam_get_authtok = is somehow returning NULL for authtok. des@ (pam maintainer in copy). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268033-7788-dhZpGqxqEK>