After using the "System files restore" my system's permissions are completely messed up

Asked by asd

I have a restore point stored on an external network drive that is 3 days old. Today I used the "System restore -> System files restore" function with options auto detection enabled. After the restore finished and I restarted the system, I was unable to sudo, because the /usr/bin/sudo owner got changed to user instead of root. I have then discovered that about 99% of the files that are not in /home/user/ now have 777 permissions and their owner is user (not root), it's almost as if systemback ran a "chmod 777 -R /".

I have never run "sudo chmod 777 -R /" in my entire history of using linux, so I am 100% sure that when this restore point was created (or any restore points prior to it) the permissions were not messed up. This happened only after the restore. I've managed to restore sudo functionality, however since almost every system now has 777 permissions and user owner it looks like the system is messed up and I'll have to do a reinstall, which is absolutely terrible.

I have another restore point that is 5 days old, but I'm afraid to restore now, I don't know what to do, maybe someone can help me.

I'm running Ubuntu 16.04 x64

Question information

Language:
English Edit question
Status:
Solved
For:
Systemback Edit question
Assignee:
No assignee Edit question
Solved by:
asd
Solved:
Last query:
Last reply:
Revision history for this message
Kendek (nemh) said :
#1

The Systemback supports only the local drives for the restore points, you need to use a partition with limitation-free filesystem. The Systemback checks this when you select a new storage directory. The restore point creation process simply copy the files with the permissions. If the permissions will be different in the restore points, the restoration process will modify the system files.
So now, if you have a correct restore point, using it to repair your broken system.

Revision history for this message
asd (731-w) said :
#2

I've mounted my network drive as a local drive under /media/data/, which allowed me to choose it in Systemback as the storage drive for the restore points. All my restore points are stored on that drive. Are you saying that I should use the "System repair" function in systemback to fix my system?

Revision history for this message
Kendek (nemh) said :
#3

No, I think the files permissions in the restore points are not completely correct. Currently, the NFS mount is not good for the Systemback.
Checks the permissions in the latest restore point, but if it seems mostly good, the setuid permission is definitely missing (bin/su and usr/bin/sudo).

Revision history for this message
asd (731-w) said :
#4

Looks like I'm going to have to reinstall the system, then.

Please add a check for the storage device filesystem type or add a warning of some sort in the next version of Systemback.