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