I did this:
 # adduser keir
  [ answer the prompts ]
 #

Then:
 # id keir
 uid=1011(keir) gid=1020(keir) groups=1020(keir)

But this doesn't work because pam_mask requires the ids to be
identical.  And I agree with pam, really.

adduser should pick the first value which is available as both a uid
and a gid.

Ian.

severity 643561 minor
thanks

I wrote:

libpam-modules 1.1.1-6.1 says:

 | If the user is not root, and the user ID is equal to the group ID,
 | and the username is the same as primary group name, the umask group
 | bits are set to be the same as owner bits (examples: 022 -> 002,
 | 077 -> 007).

But libpam-modules 1.1.3-2 says:

 | If the user is not root and the username is the same as primary
 | group name, the umask group bits are set to be the same as owner
 | bits

So matching ids is no longer needed in recent pam for correct
functioning of the pam_umask module.  However, I still think the lack
of matching ids is at the very least ugly and confusing.  It would be
nice if adduser would try to make the ids match.

I'm downgrading my bug report.

Ian.

severity #583976 minor
merge #643561 #583976
thanks