search

sgan81 / apfs-fuse

FUSE driver for APFS (Apple File System)
GNU General Public License v2.0
1.78k stars 164 forks source link

Unable to init container due to "Initialization of KeyManager failed." #105

Open fizzyduck opened 5 years ago

fizzyduck commented 5 years ago

I was hoping to use apfs-fuse to access an encrypted APFS partition (I have the correct recovery key).

Natively under OS X there is an issue when trying to unlock the volume. diskutil reports

Error unlocking APFS volume: the supplied volume is not FileVaulted

A Google search suggests that no one has come across this specific error before.

Back to apfs-fuse - I can't seem to enable any additional debug logging using -d to get any further hints as to why Initialization of KeyManager failed.. What would be a sensible next step to diagnose this further?

Here is the complete output:

$ ./apfs-fuse /mnt/in/macos.dd /mnt/mac -d 31
Found valid GPT partition table. Looking for APFS partition.
starting LoadKeybag
Initialization of KeyManager failed.
Unable to load container.
Banaanhangwagen commented 5 years ago

How did you take the image? Is your imaged-device equipped with the T2-security chip? If you execute on a macOS host:

$ hdiutil attach –nomount /Volumes/apfs_image/apfs.dmg
$ diskutil apfs list

do you get a correct listing of the container with different Volumes? Or an error?

(My guess would be that the device you imaged is equipped with the T2-security chip.)

sgan81 commented 4 years ago

That would be my guess as well ... because in that case, the keybag is encrypted in a way I haven't figured out yet, and I don't have any T2 hardware to do so ...

xxxmonsterxxx commented 10 months ago

That would be my guess as well ... because in that case, the keybag is encrypted in a way I haven't figured out yet, and I don't have any T2 hardware to do so ...

hi, maybe you have some news about cases with T2 chip?