I am not sure. At least /usr/lib/libgcc_s.so.1 have 0644 permission both on a working as well as faulty IPFire here. I have also checked various other permissions, and I did not spot an 0700 permissions.
After reading all those threads about problems with wrong file/folder permissions, I wonder if I should upgrade from 156 to 158?
Do those reported issues apply to all upgrades for version 158 or will I hit the same problems already when pakfire is upgrading to 157?
Or is it merely an issue with the jump from core 157 to 158?
Right now, Iām clueless and uncertain whether to upgrade or not.
I always run a backup prior to updating, however, Iām using some custom settings like firewall.local (was it that name?) and I have many Python scripts for monitoring in place and much more.
All of them probably donāt find their way into any IPFire backup, I guess.
Nevertheless, Iām backing up the whole machine using rsync from a remote server. At least, this should save my custom settings as well.
Which of these folders require a change of the permission to 755?
BTW my hardware is an APU4D4. Recently at core 156 I did a migration from a 32bit IPFire to a 64bit IPFire architecture. At that time I restored the 32Bit backup to the new 64bit installation of IPFire.
There is also an exclude.user file so if you have a directory that you want to backup most but not all files then you can add the directory into the include.user file and the files you donāt want backed up in exclude.user
Saves having to enter multiple filenames or if tge filenames to be backed up change over time.
Yes, you should always upgrade. This bug is affecting only a very small fraction of people and we have to get to the bottom of it, but the update is generally healthy and does not introduce any other known regressions.