-
Notifications
You must be signed in to change notification settings - Fork 193
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
CentOS 7 fuse-dislocker 0.5.1-2.el7 double free on Windows 10 standard TPM encrypted volume #102
Comments
Hi, |
Hi, |
I might have not been entirely clear here. |
For what it's worth, I don't think that you understood in my case that it
had been so already. The drive was successfully encrypted using bitlocker
in Windows, but it still hit this double-free. I had honestly just given up
and used more crude methods within Windows itself and with the Windows
recovery environment to solve the problems I needed to open the drive for.
It was much more crude than it would have been with all of the file and
filesystem tools available in Linux, had I been able to open the drive with
Dislocker.
…On Sat, Dec 2, 2017, 05:23 Aorimn ***@***.***> wrote:
I might have not been entirely clear here.
The workaround is to resume the *encryption process* done by Windows and
wait for it to finish, *then* reboot on linux and use dislocker.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#102 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA0zW_4NC4Iv-VwwbMKH1VpAdeyBMuWOks5s8UFbgaJpZM4L7Yxk>
.
|
Thanks @nealian for your reply, I indeed did not understood this for you. |
The same thing happens with a recovery-password method.
The text was updated successfully, but these errors were encountered: