On 2023-12-07 23:54, Darryl Gregorash wrote:
On 2023-12-07 16:18, Bengt Gördén wrote:
On 2023-12-07 22:27, Darryl Gregorash wrote:
Well, Knurpht's reply to you certainly clarifies things for me, yet you seem intent on arguing with him too.
He's wrong.
I upgraded my wife's 15.4 to 15.5 today. I can guarantee you that neither I nor she has ever changed anything in /etc on her computer. 15.4 was a complete fresh install, as it was a shiny new computer..
I hadn't run rpmconfigcheck yet. Here it is.
# rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew
I ran rpmconfigcheck for the first time ever today, and I got several items in the return. I checked the .rpmnew files against the config files in current use, and found several differences. There do not seem to be any essential differences between the two, in any that I checked, and the old config files, which are still in use, are still working properly.
Of course the old files will be working properly, but they are the old config files. The changes to the config are not applied in your machine. In postfix most of the changes are in the comments, but sometimes a default changes, and it is simply not applied if you keep using the old file. So you, as the admin, have to check them after any upgrade and sometimes even after an update. Sometimes there have been security patches for attacks in the wild changing a config; unless you review these files, you keep running the vulnerable version. This happened, for instance, with ntpd.conf several years ago. A typical security component with changes not applied is apparmor. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)