-
Notifications
You must be signed in to change notification settings - Fork 155
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
error 24 #421
Comments
Hi, thanks for reaching out. Can you explain a bit about why you want to do this? It seems that somebody or something changed or rolled back (parts of) your file system to an earlier version and did so by changing the encrypted files directly, not going through the mounted cryfs process. Did you recover from a backup? In that case it would be benign. Or maybe some application on your computer decided to do that for you. Another possibility is that some attacker modified your data, that would be less benign. You have three options:
In almost all cases, option 1 or 2 are the recommended options but I don't know enough about what happened in your scenario and what security guarantees you need to really make a recommendation. |
Actual Behavior
i have this message:
Error 24: There was an integrity violation detected. Preventing any further access to the file system. This can either
happen if an attacker changed your files or rolled back the file system to a previous state, but it can also happen if
you rolled back the file system yourself, for example restored a backup. If you want to reset the integrity data (i.e.
accept changes made by a potential attacker), please delete the following file before re-mounting it:
/home/USER/.local/share/cryfs/filesystems/XXXXXXXXXXXXXXXX/integritydata
Question:
If i don't want to delete the ../integritydata File, i cannot get access to my file.
so how to keep the previous version an access to it?
Steps to Reproduce the Problem
Specifications
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
The text was updated successfully, but these errors were encountered: