From: Dmitry <golubovsky@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Provide PAM configuration files in the fs skeleton
Date: Mon, 13 Aug 2012 22:24:49 -0400 [thread overview]
Message-ID: <1344911089-31197-2-git-send-email-golubovsky@gmail.com> (raw)
In-Reply-To: <1344911089-31197-1-git-send-email-golubovsky@gmail.com>
The default PAM configuration file requires valid user accounts with
non-blank passwords.
The PAM configuration file for busybox login allows local authentication
with blank passwords thus emulating the non-PAM login configuration.
Signed-off-by: Dmitry <golubovsky@gmail.com>
---
fs/skeleton/etc/pam.d/default | 8 ++++++++
fs/skeleton/etc/pam.d/login | 9 +++++++++
2 files changed, 17 insertions(+), 0 deletions(-)
create mode 100644 fs/skeleton/etc/pam.d/default
create mode 100644 fs/skeleton/etc/pam.d/login
diff --git a/fs/skeleton/etc/pam.d/default b/fs/skeleton/etc/pam.d/default
new file mode 100644
index 0000000..0bd5ba0
--- /dev/null
+++ b/fs/skeleton/etc/pam.d/default
@@ -0,0 +1,8 @@
+#
+# default; standard UN*X access
+#
+auth required pam_unix.so
+account required pam_unix.so
+password required pam_unix.so
+session required pam_unix.so
+
diff --git a/fs/skeleton/etc/pam.d/login b/fs/skeleton/etc/pam.d/login
new file mode 100644
index 0000000..d65a9d4
--- /dev/null
+++ b/fs/skeleton/etc/pam.d/login
@@ -0,0 +1,9 @@
+#
+# login: allow local logins to users with entries in /etc/passwd and
+# /etc/shadow even with null password
+#
+auth required pam_unix.so nullok
+account required pam_unix.so nullok
+password required pam_unix.so nullok
+session required pam_unix.so nullok
+
--
1.7.2.5
next prev parent reply other threads:[~2012-08-14 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 2:24 [Buildroot] [PATCH 1/2] PAM support in Busybox if linux-pam is built Dmitry
2012-08-14 2:24 ` Dmitry [this message]
2012-08-14 13:41 ` [Buildroot] [PATCH 2/2] Provide PAM configuration files in the fs skeleton Thomas Petazzoni
2012-08-14 13:50 ` Dmitry Golubovsky
2012-08-15 3:39 ` Dmitry Golubovsky
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=1344911089-31197-2-git-send-email-golubovsky@gmail.com \
--to=golubovsky@gmail.com \
--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