You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there any protection mechanisms in place that would prevent that loaded keys are saved to disk in case of a swap / hibernation / core dumps?
For example, swap or hibernation data is stored in the VM volume, and even when FileVault is activated, the VM remains unencrypted:
FileVault 2 encrypts only the OS/User volume while leaving Preboot, Recovery, and VM unencrypted.
This means sensitive key material could be exposed if stored unencrypted in the case of swap or hibernation.
The /cores directory (link 1, link 2) seems in my case to be stored in the Data volume (mounted on /System/Volumes/Data), which is encrypted.
But also here it would be interesting to know whether a ZFS key might be saved there, too, in case of a core dump caused by a crash.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Are there any protection mechanisms in place that would prevent that loaded keys are saved to disk in case of a swap / hibernation / core dumps?
For example, swap or hibernation data is stored in the VM volume, and even when FileVault is activated, the VM remains unencrypted:
This means sensitive key material could be exposed if stored unencrypted in the case of swap or hibernation.
The
/coresdirectory (link 1, link 2) seems in my case to be stored in the Data volume (mounted on/System/Volumes/Data), which is encrypted.But also here it would be interesting to know whether a ZFS key might be saved there, too, in case of a core dump caused by a crash.
All reactions