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

Initialization of KeyManager failed. #133

Open
o8ruza8o opened this issue Oct 1, 2020 · 5 comments
Open

Initialization of KeyManager failed. #133

o8ruza8o opened this issue Oct 1, 2020 · 5 comments

Comments

@o8ruza8o
Copy link

o8ruza8o commented Oct 1, 2020

Thank you so much for this project! I truly appreciate it.

First, I would like to contribute to your readme as I just got a brand new mbp from work and this is literaly the first thing I am building on it's blank state I could tell you are missing:

sudo apt install libfuse3-3 libz-dev

I won't PR for that small change.

Also, a bug report as it does not work for me, failing with:

Initialization of KeyManager failed.
Unable to load container.

And giving no useful info in gdb even with -d 1 option:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Opening device /dev/nvme0n1p2 failed with error Permission denied
Error opening device!
[Inferior 1 (process 20883) exited with code 01]
(gdb) bt
No stack.

I would be grateful for your help. Thank you!

@HLFH
Copy link

HLFH commented Jan 5, 2021

Same issue on ArchLinux (that is on BTRFS fs)

➜ ~ apfs-fuse /dev/nvme0n1p2 /mnt/apfs
Initialization of KeyManager failed.
Unable to load container.
➜ ~ uname -r
5.10.4-arch2-1
➜ ~ fdisk -l
Disque /dev/nvme0n1 : 1,82 TiB, 2001111162880 octets, 488552530 secteurs
Modèle de disque : APPLE SSD AP2048M
Unités : secteur de 1 × 4096 = 4096 octets
Taille de secteur (logique / physique) : 4096 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : gpt
Identifiant de disque : 8D0FADE6-1DB1-458B-ABE3-359F53640C28

Périphérique Début Fin Secteurs Taille Type
/dev/nvme0n1p1 6 76805 76800 300M Système EFI
/dev/nvme0n1p2 76806 244217430 244140625 931,3G APFS Apple
/dev/nvme0n1p3 244217600 464920575 220702976 841,9G Système de fichiers Linux
/dev/nvme0n1p4 464920576 488552447 23631872 90,1G Données de base Microsoft

@ahripanto
Copy link

Are u targeting a Mac with T2 Secure chip?
For Macs with T2, you need to extract the Keybag from the secure enclave.
After that, I have no idea how to combine this to get the hash.
Take a look at this Hashcat post:
https://hashcat.net/forum/thread-9775.html

@HLFH
Copy link

HLFH commented Jan 20, 2021

@ahripanto Yes I do have a Mac Mini 2018 with T2 Secure chip. But it is not encrypted. Are you sure in that case, I need to extract the Keybag from the secure enclave?

@xxxmonsterxxx
Copy link

Are u targeting a Mac with T2 Secure chip? For Macs with T2, you need to extract the Keybag from the secure enclave. After that, I have no idea how to combine this to get the hash. Take a look at this Hashcat post: https://hashcat.net/forum/thread-9775.html

Hi, any new solution for mac with t2? Now im trying to recover my data and finding some tools for this.

@xxxmonsterxxx
Copy link

@ahripanto Yes I do have a Mac Mini 2018 with T2 Secure chip. But it is not encrypted. Are you sure in that case, I need to extract the Keybag from the secure enclave?

Maybe did you have already any idea for this thread? :/

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

4 participants