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: Fri, 18 Dec 2015 08:24:32 +0000 [thread overview]
Message-ID: <bug-8536-163-dy1hqMtocL@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 #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
(In reply to James Knight from comment #1)
Our sudo package is already automatically installing a /etc/pam.d/sudo file,
see:
ifeq ($(BR2_PACKAGE_LINUX_PAM),y)
define SUDO_INSTALL_PAM_CONF
$(INSTALL) -D -m 0644 package/sudo/sudo.pam
$(TARGET_DIR)/etc/pam.d/sudo
endef
So I guess the bug reporter expect things to work properly out of the box.
James, did you test with the /etc/pam.d/sudo file installed by default by
Buildroot?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-12-18 8:24 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 [this message]
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-dy1hqMtocL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox