All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15316] New: xscreensaver should check if linux-pam is enabled
Date: Fri, 03 Feb 2023 16:20:41 +0000	[thread overview]
Message-ID: <bug-15316-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15316

            Bug ID: 15316
           Summary: xscreensaver should check if linux-pam is enabled
           Product: buildroot
           Version: 2022.11.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: jbittner.br.bugs@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

At present, xscreensaver needs to be setuid root to read /etc/shadow to handle
login verification for screen locking.  By having xscreensaver check if
linux-pam is enabled and adding --with-pam to ./configure, screen locking can
be enabled without setuid.

Note: the relevant utility from linux-pam, unix_chkpwd *DOES* need to be setuid
root

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-02-03 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 16:20 bugzilla [this message]
2024-06-15 15:05 ` [Buildroot] [Bug 15316] xscreensaver should check if linux-pam is enabled bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15316-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.