New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CRITICAL BUG] Triggering a backup chmods / to 700, causing immediate crash & unbootable PC #974
Comments
Here a
But I confirmed: The hostname is clearly resolvable?!?
|
3 weeks with a disabled backup. Issue occurred after updating distribution and maybe the rsync update is the culprit (3.1.1 → 3.1.2)? |
I discovered the same issue recently after having updated to backintime 1.2.1 under Debian Bullseye. In bug #946349 I've described how to reproduce the issue and what I believe is its root cause. You will find a patch attached to #946349 fixing things for me. Please consider integrating it in the upcoming release. P.S.: It seems to me #954 is about the same flaw. Cheers, |
This measure especially protects the root of a already mounted file system (ssh or encfs) from getting its access permissions altered. Should fix bit-team#974 and bit-team#954
Awesome, @68420948 – i created a Github merge request to ease things for the maintainer. |
Problem description
Starting a backup changes the permission of
/
from755
to700
which makes the PC immediately crash, (shells crash, windows closes) and makes the PC unbootable. I needed several hours to figure out the problem and then was finally able to pinpoint it down to BIT as problem source.Due to the changes permission, any non-root user cannot access / execute any command, unless you boot a live CD and restore the original permissions of the root-directory of the root partition.
Debug
Here is the full terminal output:
The text was updated successfully, but these errors were encountered: