Hi, Quoting Helmut Grohne (2020-09-06 09:48:26) > Another benefit of this change (if a static uid is allocated) is that we > improve reproducible installations where currently uids may depend on > configuration order. I'm very interested in having this bug fixed because of the reason above. And there is yet another use-case that would be solved by the _apt user being shipped by base-passwd: since apt would no longer require adduser, we would automatically get DPKG_ROOT support for Essential:yes packages plus apt. What do we need to implement this change? I observed that when I apply this patch to base-passwd: diff -Nru base-passwd-3.5.51/passwd.master base-passwd-3.5.51+nmu1/passwd.master --- base-passwd-3.5.51/passwd.master 2021-07-10 13:57:43.000000000 +0200 +++ base-passwd-3.5.51+nmu1/passwd.master 2021-08-24 20:08:52.000000000 +0200 @@ -15,4 +15,5 @@ list:*:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin irc:*:39:39:ircd:/run/ircd:/usr/sbin/nologin gnats:*:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin +_apt:*42:42::/nonexistent:/usr/sbin/nologin nobody:*:65534:65534:nobody:/nonexistent:/usr/sbin/nologin Then not only will the _apt user be created as expected, but I also observed that when upgrading base-passwd on a system with an existing _apt user with uid 100 from basepasswd 3.5.51 to my patched 3.5.51+nmu1, the uid of the _apt user remained the same as it should. Is my observation correct or is anything else missing? Thanks! cheers, josch P.S.: I also want to highlight, how fitting it would be to have the apt uid be The Answer to Life, the Universe and Everything. ;)
Attachment:
signature.asc
Description: signature