[Bug 1081323] Re: /bin/sh illegal option -p when using pam_namespace.so

[Scott Duckworth]

The attached patch removes the -p option from the shebang line of
/etc/security/namespace.init and fixes this bug.  The effect of the -p
option with bash is to not reset the effective UID to match the real UID
if they are different, but this is the default behavior if bash is
invoked as /bin/sh.  Similarly, this is also the default if dash is
invoked as /bin/sh.  So the -p option is extraneous in the first place
and causes warnings if dash is being used for /bin/sh.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1081323

Title:
  /bin/sh illegal option -p when using pam_namespace.so

Status in “pam” package in Ubuntu:
  Triaged
Status in “pam” package in Debian:
  New

Bug description:
  When PAM is configured to use pam_namespace.so, something, presumably
  PAM, emits the line "/bin/sh: 0: Illegal option -p" once for every
  entry defined in /etc/security/namespace.conf.  Switching /bin/sh from
  dash to bash using dpkg-reconfigure dash avoids the problem.

  I have seen this problem when authenticating with login, sudo, and su,
  but not with ssh (sshd is configured with UsePAM yes).

  Is it possible that pam_namespace.so is making the assumption that
  /bin/sh is implemented by bash?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1081323/+subscriptions