-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
zdb -dAdvv hides file attributes (e.g. mode) for encrypted datasets (even when keys are loaded) #12707
Labels
Comments
riyad
changed the title
zdb -dAdvv hides file attributes (e.g. mode) for encryted datasets (even when keys are loaded)
zdb -dAdvv hides file attributes (e.g. mode) for encrypted datasets (even when keys are loaded)
Oct 30, 2021
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
behlendorf
added
Bot: Not Stale
Override for the stale bot
and removed
Status: Stale
No recent activity for issue
labels
Nov 1, 2022
behlendorf
pushed a commit
that referenced
this issue
Mar 2, 2023
The approach is straightforward: for dataset ops, if a key was offered, find the encryption root and the various encryption parameters, derive a wrapping key if necessary, and then unlock the encryption root. After that all the regular dataset ops will return unencrypted data, and that's kinda the whole thing. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Jorgen Lundman <lundman@lundman.net> Signed-off-by: Rob Norris <robn@despairlabs.com> Closes #11551 Closes #12707 Closes #14503
lundman
pushed a commit
to openzfsonwindows/openzfs
that referenced
this issue
Mar 3, 2023
The approach is straightforward: for dataset ops, if a key was offered, find the encryption root and the various encryption parameters, derive a wrapping key if necessary, and then unlock the encryption root. After that all the regular dataset ops will return unencrypted data, and that's kinda the whole thing. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Jorgen Lundman <lundman@lundman.net> Signed-off-by: Rob Norris <robn@despairlabs.com> Closes openzfs#11551 Closes openzfs#12707 Closes openzfs#14503
pcd1193182
pushed a commit
to pcd1193182/zfs
that referenced
this issue
Sep 26, 2023
The approach is straightforward: for dataset ops, if a key was offered, find the encryption root and the various encryption parameters, derive a wrapping key if necessary, and then unlock the encryption root. After that all the regular dataset ops will return unencrypted data, and that's kinda the whole thing. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Jorgen Lundman <lundman@lundman.net> Signed-off-by: Rob Norris <robn@despairlabs.com> Closes openzfs#11551 Closes openzfs#12707 Closes openzfs#14503
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
System information
Describe the problem you're observing
Trying to determine if I'm affected by a data corruption bug (#11474) I had to see if file modes had weird values. Running the test command
zdb -dAdvv $FILESYSTEM | grep 'mode\s\+[0-9]' | sort | uniq -c
I learned that zdb doesn't show this information for encrypted datasets at all. Instead placeholders like "(bonus encrypted)" and "(object encrypted)" are printed even when the dataset keys are loaded and the datasets are mounted.Describe how to reproduce the problem
Run
zdb -dAdvv
on an enctypted dataset:The text was updated successfully, but these errors were encountered: