Hi Anton,
I rebuilt from a fresh cvs checkout just now:
% ntfsdecrypt --version
ntfsdecrypt v2.0.0 (libntfs 10:0:0) - Decrypt files and print on the
standard output.
% ./ntfsdecrypt -k /home/...pfx /dev/sda1 "dir/file"
Enter the password with which the private key was encrypted: *********
There are no entries in the DRF array.
Failed to obtain file encryption key. Aborting.
I was sort of afraid this might be the outcome, but I'm not sure what to
do at this point. The files on /dev/sda1 were copied from Windows XP as
encrypted backup files. Later my original drive has crashed, but I had
saved off the PFX file and had my password stored safely away. So I
don't have access to the original profile on that machine with its SID
or whatever. Is it the case I might not have backed up certain key files
(i.e. the one containing the FEK)? If so, am I hosed or is there still hope?
Matt
Anton Altaparmakov wrote:
> Hi,
>
> On 17 Sep 2007, at 14:34, Matthew A. Postiff wrote:
>> % ntfsdecrypt --version
>>
>> ntfsdecrypt v1.13.1 (libntfs 9:0:0) - Decrypt files and print on the
>> standard output.
>>
>> % ntfsdecrypt -k /home/...pfx /dev/sda1 "dir/file"
>> Enter the password with which the private key was encrypted: **********
>> Failed to remove PKCS#1 padding from decrypted file encryption key.
>> Failed to decrypt the file encryption key.
>> Failed to obtain file encryption key. Aborting.
>>
>> What can I do now?
>
> Please try the latest version (in CVS) or even better wait a few days
> for us to release ntfsprogs 2.0.0 and then try with them.
>
> Best regards,
>
> Anton
|