Well, seems like the permissions of the package are 0750 (just check by downloading the package). So: 1. the package updates and the permissions get set to 0750 (because these are the permissions inside the rpm) 2. the scripts checks, complains that its wrong and corrects it 3. repeat Am 10.08.23 um 23:39 schrieb Joe Salmeri:
On 8/10/23 16:11, Carlos E. R. wrote:
On 2023-08-10 21:16, Joe Salmeri wrote:
Although I am reporting this after updating to 20230809, these wrong permissions messages have occurred for a long time ( years )
For TW 20230809 the message was
/usr/bin/fusermount3: setting to root:trusted 4755 (wrong permissions 4750)
I cannot remember doing a TW update where I didn't receive a message about wrong permissions similar to that one.
The issue is that these messages are wrong.
I have confirmed this multiple times.
When I update my test system and see these kinds of messages, I check the permissions on my main desktop system to see if they are wrong there ( they aren't )
Then when I update the main desktop system, I get the same messages for the files that I already confirmed were not wrong before doing the update.
Here were the permissions on the main desktop system BEFORE updating to TW 20230809 which show that it was root:trusted 4755
-rwsr-xr-x 1 root trusted 35K Jul 17 13:34 /usr/bin/fusermount3
It seems that whatever does the permission check is what is broken but I am unsure what that is.
Is this a known bug/problem? If not, any idea what I need to report the bug against ?
Guess:
The package comes with a set of permissions.
At some point, "chkstat --system" runs. This was a script that was, in old times, part of SuSEconfig. This script checks permissions against a list, in /etc/permissions.easy and /etc/permissions.local by default. If the permissions in the just installed package do not match those in the list, they are changed, and it prints that message, "wrong permissions". As it fixes them, you do not see any problem when you check them.
cer@Telcontar:~> grep /usr/bin/fusermoun /etc/permissions.easy /usr/bin/fusermount root:trusted 4755 /usr/bin/fusermount3 root:trusted 04755 cer@Telcontar:~>
Hi Carlos,
Thanks very much for that information as I was not sure what was doing the check.
I get what it is doing, my point was that it is complaining that the permissions were WRONG, however, I checked them BEFORE I did the update because the message came up on a different TW system.
So BEFORE I did the update to TW 20230809, the permissions where already 4755, however, when the update runs it complains that they are 4750 and says it is setting them to 4755.
This was not a one time situation, I see this come up with pretty much every TW update I have ever done.
Also, since I am using btrfs I can also look at the BEFORE snapshot which also confirms that permissions were 4755 before the update
-rwsr-xr-x 1 root trusted 35K Jun 14 13:20 /.snapshots/2/snapshot/usr/bin/fusermount -rwsr-xr-x 1 root trusted 35K Aug 9 14:25 /usr/bin/fusermount3
So it would appear that checkstat has a bug in which it is incorrectly reporting the before permissions as 4750 when in fact that were really 4755.
Actually I think you may have just pointed out what could be trigger the bug.
permissions.easy has fusermount3 permissions as 04755 but shouldn't that be 4755 ?
permissions.secure has fusermount3 permissions as 04750 but shouldn't that be 4750 ?
Shouldn't permission values be 4 digits not 5 ?
-- Regards,
Joe
Sincerely Kilian Hanich