Skip to content
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

Files moved out of unlocked encrypted directory cannot be accessed (Required key not available) #419

Open
richardjharris opened this issue Dec 27, 2024 · 1 comment

Comments

@richardjharris
Copy link

richardjharris commented Dec 27, 2024

I am not exactly sure what happened. I think I drag and dropped a directory within an fscrypt-encrypted, unlocked directory, to another place. The files have their standard plaintext names and were moved from an unlocked directory. When I try to read or write to them, I get 'Required key not available'.

Kernel is 6.12.4

I still have all the protectors that were used loaded, created one directory per protector and unlocked it, but the files still cannot be accessed.

@ebiggers
Copy link
Collaborator

Yes, it is possible to end up with encrypted files outside an encrypted directory this way. (It is not recommended to do this.) They remain encrypted by the same encryption policy as before, so you can unlock them by running fscrypt unlock on any directory uses the same encryption policy, such as the one that they were moved out of originally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants