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: Thu, 17 Dec 2015 16:43:04 +0000 [thread overview]
Message-ID: <bug-8536-163-dM6KImwQ8X@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 #1 from James Knight <james.knight@rockwellcollins.com> ---
I'm not a PAM expert, but I assume if you're integrating PAM support into sudo,
I believe it requires the respective PAM configuration for sudo to work
(/etc/pam.d/sudo). If anyone knows that this is not the case, I'd be interested
to know.
Trying to reproduce, building with "--without-pam", I can configure a default
user to perform sudo operations. If I build with "--with-pam" and I do not have
"/etc/pam.d/sudo" configured, all requests are denied. If I use the
"--with-pam" build with "/etc/pam.d/sudo" configured, it works fine. Is this
what you are experiencing?
If integrating PAM support into sudo requires PAM configuration (ie. cannot
fall back onto just sudo configuration), I'm curious if you have a desired use
case to not include PAM support for sudo (while having other packages use it as
well). If this is a the case, maybe there should be a configuration option
which defaults to include PAM support (when the PAM package exists) which can
be explicitly disabled by the developer.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-12-17 16:43 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 ` bugzilla at busybox.net [this message]
2015-12-18 8:24 ` [Buildroot] [Bug 8536] " 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
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-dM6KImwQ8X@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.