On Wed, 2019-01-16 at 17:25 +0000, M. J. Everitt wrote: > On 16/01/19 12:59, Joakim Tjernlund wrote: > > On Wed, 2019-01-16 at 12:20 +0000, M. J. Everitt wrote: > >> On 16/01/19 11:58, Joakim Tjernlund wrote: > >>> How come portage isn't in shadow, only in passwd ? > >>> Seems wrong to me. > >>> > >>> Jocke > >> Because the portage user never logs on .. hence has no password. That said, > > That goes for evry other system account too but these are in shadow. > > > >> it does seem an odd situation, since even users with no password do tend to > >> appear in /etc/shadow .. perhaps it was/is never "properly" added as a user > >> .... > > I think/hope so. Now passwd looks like so: > > portage:x:250:250:portage:/var/tmp/portage:/bin/false > > This looks like a shadow account. Because of the missing entry passwd > > thinks this is a normal account: > > # > passwd -S portage > > portage P > > as opposed to: > > # > passwd -S daemon > > daemon L 10/28/1996 0 -1 -1 -1 > > > > Jocke > With the help of some devs, I have drilled this down to commit > https://gitweb.gentoo.org/proj/baselayout.git/commit/share.Linux/shadow?id=5ee3c95d2086e626247640ca35cf2da78c4c9846 > in baselayout in 2016. > > Some of my systems mysteriously (but predictably) are missing portage in > /etc/shadow as you describe, but these are prior to the baselayout change > above. Many have it as the commit suggests also. I suspect there may not > have been an upgrade path which added it between versions however, unless > it was pulled in via CONFIG_PROTECT somehow > > Bug https://bugs.gentoo.org/show_bug.cgi?id=521970 is also referenced in > that commit. > > Hope that answers your question (and my curiosity!). > Regards,
Sure does ! Jocke PS. I am the reporter of the above bug and I had completely forgot I had asked this before :)
