Comment 1 by ErmaC , Feb 17, 2012
Try creating the Recovery hd partition. http://www.insanelymac.com/forum/index.php?showtopic=271206 look like the encryption is also relate with the Recovery partition...
Labels:
Priority:Low
Type:Other
Priority:Medium
Type:Defect
Comment 2 by Hannah Howard, Mar 10, 2012
Fyi, i've been looking into it, and it needs more than just a recovery partition. the person who seems to be taking a shot at it somewhat is someone named RevoGirl - revogirl.wordpress.com. the problem is the entire unlocking process happens in EFI, before the kernel is loaded. basically, it's whatever logic resides in the boot.efi that sits on the recover hd (in System/Library/Coreservices). that file loads the login interface that lets you type in your password, using images which sit in so called .efires files which reside in "Recovery HD/com.apple.boot.S/usr/standalone/EFILoginUI/". it's not enough simply to install a chameleon boot loader on the recovery hd-- because currently chameleon can't perform the same logic that the boot.efi on the Recovery HD does to perform the unlock process. you'd have to add functionality to chameleon to completely emulate this process. you'd need to: 1. perform the login by loading the .efires files to create the login UI 2. actually use the password to decrypt the CoreStorage volume where the actual data lives. sounds kind of complicated and overwhelming, at least until apple releases some data about the CoreStorage format.
Comment 3 by Cosmosis Jones, May 5, 2012
Status:
WontFix
Sign in to reply to this comment.
Reported by Hannah Howard, Jan 16, 2012