[dm-crypt] iv generation from third-party code
fraser.scott at gmail.com
Wed May 6 22:28:20 CEST 2015
I had a Western Digital My Book World Edition which died a few years ago.
My wife now wants the photos that were on it :)
The good news is, the hard disk is fine. The bad news is that I used the
hardware assisted encryption on the data partition.
WD make the source code available, so I've been poking around. Thanks to
help from the peeps on ##crypto (freenode), it seems clear that the custom
device mapper module isn't using any keys store on a chip etc, it is just
using hardware for speed. It looks like it is using AES in LRW mode but
uses some sort of custom IV tweaking.
What are my chance of "porting" the IV stuff from the module to a clean
dm-crypt.c so that I can do the AES decryption in software? Given that I
don't know much C, or know much about kernel development or dm-crypt? ;) In
the meantime I am trying to source some replacement hardware.
The module was called as follows:
# echo 0 $(cat /sys/block/md4/size) ox-crypt hexkey hexiv 0 /dev/md4 0 |
dmsetup create dmmd4
(I have the key and IV)
and can be viewed here:
My attempt so far can be seen here:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dm-crypt