Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Matt Madison <matt@madison.systems>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Removing shadow breaks PAM logins
Date: Sat, 04 Apr 2015 07:36:05 -0700	[thread overview]
Message-ID: <1428158165.4354.25.camel@workhorse.madison.systems> (raw)

For one of my projects, I have a read-only rootfs, but I do use PAM
plugins for controlling login access to the device, as well as group
controls and non-root users for daemons and such.  After my latest
update to master, I ran into an problem where all logins failed and some
daemons failed to start.  I tracked it down to this recent commit:

http://cgit.openembedded.org/openembedded-core/commit/meta/lib/oe/rootfs.py?id=f4932e2e640764d16f1f6d398390ebfb376f4cf1

The problem is that the shadow package includes not only the utilities
for manipulating the password and groups files, but it also includes the
full-featured /bin/login and the su, sg, groups, and newgrp utilities,
plus the login PAM rules file.

I worked around the issue by repackaging shadow so the programs and
config files that aren't related to changing the passwd and group files
ended up in a separate package that remained in the rootfs.  That seemed
to be the cleanest way to deal with the problem, and it did the trick
for me.  If there's interest, I can submit a patch.

-Matt



             reply	other threads:[~2015-04-04 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04 14:36 Matt Madison [this message]
2015-04-04 16:06 ` Removing shadow breaks PAM logins Khem Raj

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=1428158165.4354.25.camel@workhorse.madison.systems \
    --to=matt@madison.systems \
    --cc=openembedded-core@lists.openembedded.org \
    /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