All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8536] Building sudo with PAM results in unusable sudo
Date: Mon, 21 Dec 2015 14:08:02 +0000	[thread overview]
Message-ID: <bug-8536-163-lU1g9Ohp6p@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8536-163@https.bugs.busybox.net/>

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

--- Comment #8 from Doug Kehn <rdkehn@yahoo.com> ---
Hi Everyone,

The /etc/pam.d/sudo line:
     auth        required    pam_wheel.so use_uid
requires that the user is a member of the wheel group. When sudo is built
without PAM, the PAM databases are not queried so the user does not have be a
member of wheel.

Try changing the line to:
     auth        sufficient   pam_wheel.so use_uid
or comment it out to allow non-wheel group users sudo access. The user still
has to be listed in sudoers.

Hope this helps,
...doug

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2015-12-21 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 10:00 [Buildroot] [Bug 8536] New: Building sudo with PAM results in unusable sudo bugzilla at busybox.net
2015-12-17 10:52 ` Thomas Petazzoni
2015-12-17 14:07   ` rdkehn at yahoo.com
2015-12-17 16:43 ` [Buildroot] [Bug 8536] " bugzilla at busybox.net
2015-12-18  8:24 ` bugzilla at busybox.net
2015-12-18 12:00 ` bugzilla at busybox.net
2015-12-18 14:03 ` bugzilla at busybox.net
2015-12-18 14:10 ` bugzilla at busybox.net
2015-12-18 23:32 ` bugzilla at busybox.net
2015-12-19  1:53 ` bugzilla at busybox.net
2015-12-21 14:08 ` bugzilla at busybox.net [this message]
2016-10-22 21:15 ` bugzilla at busybox.net

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-8536-163-lU1g9Ohp6p@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.