|
|||||||||||
|
From: Derek <derekm(at)rogers.com>
Date: Tue Jun 17 2003 - 15:04:09 EDT Here is a snippet from two columns copied and pasted into notepad, one per line, saved, and then converted to hex: fffedd2bb1bf52e1e4926952ad67f3d5e1e60d000a006952ad67f3d5e1e66952a d67f3d5e1e6 >From this I've guessed that "fffe" is a unicode header, which
dd2bb1bf52e1e4926952ad67f3d5e1e60d000a006952ad67f3d5e1e66952ad67f 3d5e1e6 Since the rows are CR/LF delimited we get:
dd2bb1bf52e1e4926952ad67f3d5e1e6
This file is also stored little-endian, so we get:
2bddbfb1e15292e4526967add5f3e6e1
The first is a row that contains a password, the second row contains a password of "" (0 length string) If we separate the rows where the data matches we get:
2bddbfb1e15292e4 526967add5f3e6e1
It seems that the LS = RS on the empty password line, and RS = RS between the two lines. I've tried putting in a single character password, but it seems to modify many bits in the LS. Based on this information, it seems that a 64-bit hash function is used to calculate the left side, and the right side is used to obfuscate the result of the function via XOR (which yeilds a result of 0 when LS = RS). I also presume that the value of obfuscating the results of the hash function is so that the output is not noticably predictable at a glance?
Does anyone have information that they can share to help the
progression of this train of thought, or documentation to point
me
Thanks,
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:40 EDT |
||||||||||
|
|||||||||||