Arch Linux

x-yuri

Member

Registered: 2013-01-06

Posts: 161

[SOLVED] warning: /etc/shadow installed as /etc/shadow.pacnew

I've probably figured out that it should be left alone (as it is). From what I can see the change was introduced here. Which means in filesystem-2020.05.07. Should I not change the file, right?

And well, this might be a dummy question, but do I need all this stuff in my `/etc/shadow` file?

...
systemd-coredump:!!:17190::::::
systemd-journal-remote:!!:17190::::::
systemd-journal-upload:!!:17190::::::
avahi:!:17190::::::
polkitd:!:17191:0:99999:7:::
rtkit:!:17191:0:99999:7:::
git:!:17191::::::
postgres:!:17195:0:99999:7:::
mysql:!!:17195::::::
deluge:!:17198:0:99999:7:::
munin:!:17253::::::
uuidd:!!:17277::::::
dbus:!!:17277::::::
clamav:!:17296::::::
usbmux:!:17429:0:99999:7:::
colord:!:17506:0:99999:7:::
systemd-network:!!:17550::::::
ftp:!!:17550::::::
http:!!:17550::::::
nobody:!!:17550::::::
bin:!!:17550::::::
systemd-resolve:!!:17550::::::
mail:!!:17550::::::
daemon:!!:17550::::::
cups:!!:17605::::::
tinyproxy:!!:17605::::::
systemd-timesync:!!:17851::::::
lightdm:!!:17930::::::
geoclue:!!:17931::::::
influxdb:!!:17932::::::
mongodb:!!:18054::::::
dhcpcd:!!:18406::::::

Last edited by x-yuri (2020-05-25 08:24:16)

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [SOLVED] warning: /etc/shadow installed as /etc/shadow.pacnew

I've probably figured out that it should be left alone (as it is). From what I can see the change was introduced here. Which means in filesystem-2020.05.07. Should I not change the file, right?

Well, the change in question seems like a useful one, so perhaps you should consider manually adding it to your system.

And well, this might be a dummy question, but do I need all this stuff in my `/etc/shadow` file?

I don't understand the question, are you asking if you can safely delete those users using userdel?

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

x-yuri

Member

Registered: 2013-01-06

Posts: 161

Re: [SOLVED] warning: /etc/shadow installed as /etc/shadow.pacnew

Well, the change in question seems like a useful one, so perhaps you should consider manually adding it to your system.

Oh, forgot to mention. I'm using su occasionally, so the field is non-empty anyway in my case.

I don't understand the question, are you asking if you can safely delete those users using userdel?

I probably had the following change in mind (Remove systemd provided users and groups?). A number of users where removed from /etc/passwd. So I thought that maybe not all the lines are necessary in /etc/shadow as well. I didn't mean removing users. I didn't expect "no line, no user", which you apparently imply.

And now that I look into /etc/passwd, all those removed (systemd provided) users are there. Which apparently means they were removed from the package, but added automatically by systemd anyway.

Last edited by x-yuri (2020-05-25 08:23:29)

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [SOLVED] warning: /etc/shadow installed as /etc/shadow.pacnew

Well, the change in question seems like a useful one, so perhaps you should consider manually adding it to your system.

Oh, forgot to mention. I'm using su occasionally, so the field is non-empty anyway in my case.

Then you definitely don't want to revert to the stock behavior of a disabled password.

I don't understand the question, are you asking if you can safely delete those users using userdel?

I probably had the following change in mind (Remove systemd provided users and groups?). A number of users where removed from /etc/passwd. So I thought that maybe not all the lines are necessary in /etc/shadow as well. I didn't mean removing users. I didn't expect "no line, no user", which you apparently imply.

And now that I look into /etc/passwd, all those removed (systemd provided) users are there. Which apparently means they were removed from the package, but added automatically by systemd anyway.

See the big red warning at https://wiki.archlinux.org/index.php/Us … r_database

Many users have screwed up their systems by trying to handle pacnew files for passwd/shadow. These files are databases and are expected to have constantly updating content, and their pacnew files only contain the initial, at-install contents. Many of these users were moved from being statically coded to being dynamically injected via systemd-sysusers, that doesn't mean they were deleted. But users who mistakenly thought that passwd.pacnew should be handled, deleted all their users and broke their systems in the process.

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)