-
Notifications
You must be signed in to change notification settings - Fork 2
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
Stable enough? #1
Comments
@acanrpk I used FUSECry daily for the past 2 years and had no problems with it. It is currently not handling symlinks properly. Symlinks in mounted FS that point outside of mounted partition will cause errors and can be removed only by unmounting, then deleting the symlink in obfuscated directory and then mounting again. As a result, you won't be able to clone a git branch into encrypted partition for example, because it will try to link/unlink |
No need for symlink fixing, I just wanted to know about known issues from the dev themselves (that's why I tagged you, you're listed as dev on some other site). I'll play with it a bit and see if any issues come up. |
There is this one: https://www.cryfs.org/howitworks |
Yeah, that one has a long history of corrupting data upon unexpected power loss. Gonna compare the two in benchmarks and then take a decision. |
Please let me know how it went and raise any issues you find here. It will mean a lot. |
I probably won't have time for in depth comparison (block sizes, HDD vs SSD, layers of FUSE filesystems) before the next week, but I'll provide the results and issues here at the earliest! |
Tagging @predragmandic
Sorry for creating an issue, but I was wondering if FUSECry was considered stable enough for normal use?
As far as I can tell, no other FUSE FS project provides file size obfuscation while being reasonably new.
The text was updated successfully, but these errors were encountered: