Should we make the fscrypt metadata harder to delete?
Open
- Dominant language
- Go
- Stars
- 1k
- Forks
- 111
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
I was reading [this Reddit post](https://www.reddit.com/r/archlinux/comments/16y0w8e/i_accidentally_deleted_the_fscrypt_protector_on/) about how someone accidentally deleted files in their `/.fscrypt/` directory, and I was wondering if we could make this harder to do.
One method might be explicitly making the files have permissions of `0400` instead of `0600`, and then just `chmod`-ing them when we need to either destroy metadata or update a policy file when we add/update a protector.
Alternatively (or additionally), we could change the file attributes to mark the metadata files as immutable.
Contributor guide
Assessment
This issue has not been assessed yet.