From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8536] New: Building sudo with PAM results in unusable sudo
Date: Thu, 17 Dec 2015 10:00:50 +0000 [thread overview]
Message-ID: <bug-8536-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8536
Bug ID: 8536
Summary: Building sudo with PAM results in unusable sudo
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: nroach44 at gmail.com
CC: buildroot at uclibc.org
As the title, when building an image with both sudo and PAM results in sudo
denying all requests.
If you comment out the PAM section in sudo.mk everything works as intended
(minus any PAM integration).
I only have one file in sudoers.d that contains:
%sudo ALL=(ALL) ALL
otherwise I don't have any PAM or sudo configuration
I'm building for a SAMA5D3_XPLD (cortex-a5) board with linux 4.0.9 on latest
git, with a custom ct-ng toolchain (that otherwise works)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-12-17 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 10:00 bugzilla at busybox.net [this message]
2015-12-17 10:52 ` [Buildroot] [Bug 8536] New: Building sudo with PAM results in unusable sudo 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
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@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