|
Metadata
Block Offset |
Starting
Bytes |
helloworld.doc |
Content
Changed |
Permissions
Changed |
File
Deleted |
Shift
& Delete |
Rename |
Copy
File |
|||||||
|
0x0750000 |
94
01 |
|
0D |
|
16 |
|
16 |
|
16 |
|
16 |
|
16 |
|
16 |
|
0x0754000 |
95
01 |
Identical |
0E |
|
16 |
|
16 |
Identical |
0E |
Identical |
0E |
Identical |
0E |
Identical |
0E |
|
0x0758000 |
96
01 |
Identical |
0F |
Identical |
0F |
Identical |
0F |
Identical |
0F |
Identical |
0F |
Identical |
0F |
Identical |
0F |
|
0x075C000 |
97
01 |
Identical |
0C |
Identical |
0C |
|
17 |
Identical |
0C |
Identical |
0C |
Identical |
0C |
Identical |
0C |
|
0x07B0000 |
AC
01 |
* File Contents - not metadata |
|||||||||||||
|
0x07C0000 |
B0
01 |
No Data |
No Data |
No Data |
Deleted file reference |
No Data |
No Data |
Copied content |
|||||||
The table above (taken from the beginning of the .doc
chapter) identifies the changes between the drives at the specific offset,
relating to the metadata blocks.
The metadata block starting at 0x0750000 after the
permissions have been changed is identical to the one where contents have been
changed, with the exception of the Modified and Accessed times, as well as the
file size. When the permissions changed the file size didn't, so this remains
0A (10 bytes); the same as the file system with the original .doc file. The
next metadata block identified is a copy of the one at the previous offset,
with the only change being the first two bytes, which are used for addressing
the block.
The next metadata block identified in the table (at offset
0x0758000) is the same on all the drives. This is the same for the next offset,
with the exception of the drive where the permissions have been changed. When
the permissions have been changed this block is actually the same as the
previous (offset 0x0758000), with the exception of the Accessed time (highlighted
in green) and four bytes changed from 2B 4F FA FB 01 to 8E EB 21 E1 01 (red).
The two blocks below show this, with the top block being the earlier metadata
block and the bottom one being offset 0x075C000.
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E
0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
0007506C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 2F 27
6F 7F 2B D0 01 24 2F 27 6F 7F 2B D0 01 ................$/'o.+Ð.$/'o.+Ð.
0007506E0 24 2F 27 6F 7F 2B D0 01 24 2F 27 6F 7F 2B D0 01 20 00 00 00 00 00
00 00 00 06 00 00 00 00 00 00 $/'o.+Ð.$/'o.+Ð.
...............
000750700 02 00 00 00 00 00 00 00 2B 4F FA FB 01
00 00 00 0A 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ........+Oúû....................
00075C6C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 2F 27
6F 7F 2B D0 01 24 2F 27 6F 7F 2B D0 01 ................$/'o.+Ð.$/'o.+Ð.
00075C6E0 71 DA CB AF 88 2B D0 01 24 2F 27 6F 7F 2B D0 01 20 00 00 00 00 00
00 00 00 06 00 00 00 00 00 00 qú˯+Ð.$/'o.+Ð. ...............
00075C700 02 00 00 00 00 00 00 00 8E EB 21 E1 01
00 00 00 0A 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ........Ë!á....................
At the metadata block 0x075C000, the original drive doesn't
have a file listing in this location (nor do any of the others at this level of
test), whereas when the permissions have changed it does. As this offset is
where the majority of the differences are for the drive with the permissions
change and it is just a copy (with two changes) of the previous offset, it
could be that the bytes highlighted in red above represent the permissions
change.
They stay the same across the other drives, so a permission
change is the only action that has caused them to change.
A pattern that has occurred is that at offset 0x750050 the
byte often changes. The patterns appears to be 04 for a file in use, 06 for a
copied file, 03 for deleted file and 02 for a permanently deleted file. There
is also a pattern at offset 0x07501E0, with the byte being set to 02 when a
file is not modified, 03 when modified and 04 when copied.