![]() ![]() Then, the private key and password were blamed. The natural thing was to think that it must have been the command line options I used, the spelling of words, or the spaces. This seemed to be odd since new version of software supposed to fix problems and not break what was working just fine. Surprisingly, the newest version of the software gave an error message and refused to take the private key with the password that worked just fine in GUI.Ĭ:\temp\ftkimager> ftkimager.exe c:\temp\usb.e01 -verify -incert c:\temp\pri.pfx FTK Imager v3.1.1 CLI (Aug 20 2012)Įrror setting up decryption: DecryptWithPrivateKey: Cert encrypted and password failed: c:\temp\pri.pfx Of course, the question can come up to verify the image in the tool that created it. ![]() The image was opened in FTK Imager 3.0.1 using the private key and the given password and FTK Imager was happy to comply. Using version 3.1.1 to acquire an image on Windows 7 Professional 32/64 bit worked as it was advertised.Ĭ:\temp\ftkimager> ftkimager.exe \\.\physicaldrive1 c:\temp\usb -e01 -outcert C:\temp\pub.cerĪccessData FTK Imager v3.1.1 CLI (Aug 20 2012)Ĭopyright 2006-2012 AccessData Corp., 384 South 400 West, Lindon, UT 84042 It’s been working great, but in the latest version something has changed. It was not about the performance improvement ( since there was none ), but the OS support and the ability to encrypt images using a certificate. It was just as much exciting as finding out about Access Data’s FTK Imager CLI. ![]() I remember how excited I was to test TIM (Tableau IMager) on a multi core system and see it outperform the competition. The latest and greatest tool without testing can be a risk factor just like the old and worthless. This is not about acquisition tools, but about understanding why we need to test our tools even if the tool was just updated. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |