[Bug 1355111] Re: newgrp fails with "crypt: Invalid argument"

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=988184.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2013-07-25T02:56:36+00:00 Eric wrote:

Description of problem:
newgrp fails with "crypt: Invalid argument" even when the correct password is given

Version-Release number of selected component (if applicable):
shadow-utils-4.1.5.1-5.fc19
glibc-2.17.11.fc19

How reproducible:
100%

Steps to Reproduce:
1. Create a new group without a password, or use an existing group that doesn't have a password.  I happened to discover this using the "mock" group.
2. Add a already logged-in user to a group in /etc/group.
3. Note that the current user login session is not a member of that group, i.e., by using the "id" command at a shell prompt
4. Issue a "newgrp <groupname>" command.
5. When prompted, enter the user's password.

Actual results:
crypt: Invalid argument

Expected results:
user gets a subshell with the group in the group list (as shown by the "id" command)

Additional info:
This is due to a change in behavior in crypt() in glibc 2.17.  It has been reported upstream along with a patch that fixes it:
    https://alioth.debian.org/tracker/index.php?func=detail&aid=314234
I have locally rebuilt the RPM with that patch added, and it solves the crypt problem.  The patch applied cleanly with -p1.

Note that with the crypt problem solved, newgrp then gives different errors:
    setgroups: Operation not permitted
    setgid: Operation not permitted
However, that is a completely independent bug or configuration error that I am still investigating.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/0

------------------------------------------------------------------------
On 2013-07-25T02:58:20+00:00 Eric wrote:

Oops, this is in the Debian Alioth tracker, not bugs.debian.org.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/1

------------------------------------------------------------------------
On 2013-07-25T12:12:38+00:00 Tomas wrote:

It is really weird how you could get this error. If the user is member
of the group, he will never be prompted for a password when newgrp
groupname is issued. And when he is not and there is no password in
group/gshadow set this bug will just affect the message issued. Though
applying the patch is correct thing as crypt: Invalid argument is not a
particularly good message.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/2

------------------------------------------------------------------------
On 2013-07-25T15:46:54+00:00 Eric wrote:

The case is that the user was not a member of the group at login, but
was added to /etc/group after login, then using newgrp to get a subshell
with that group added. Doesn't the user get prompted for their own
password in that case?  I think I last experienced this use case with
F14, and I don't remember whether I was prompted for a password or not.
I might fire up F14 in a VM to check.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/3

------------------------------------------------------------------------
On 2013-07-25T18:27:59+00:00 Tomas wrote:

Nope, there should not be a prompt in such situation and it isn't
according to my testing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/4


** Changed in: shadow
       Status: Unknown => Invalid

** Changed in: shadow
   Importance: Unknown => Undecided

** Bug watch added: alioth.debian.org/ #314234
   http://alioth.debian.org/support/tracker.php?aid=314234

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

Title:
  newgrp fails with "crypt: Invalid argument"

Status in Shadow:
  Invalid
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  entry from /etc/passwd:
  user:x:1000:1000:User,,,:/home/user:/bin/bash

  entry from /etc/group:
  dummy:x:200:user

  entry from /etc/gshadow:
  dummy:*::

  logged on as user the command
  "newgrp dummy" asks for a password and fails with "crypt: Invalid argument"

  after removing the line for dummy from gshadow newgrp works

  
  A similar bug was reported on the redhat tracker: https://bugzilla.redhat.com/show_bug.cgi?id=988184

  
  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04 LTS"

To manage notifications about this bug go to:
https://bugs.launchpad.net/shadow/+bug/1355111/+subscriptions