K... I think there may be a weakness!!!!, if I understand the code correctly...
HC
If you find one, please share!
Well I'd started and my F***** RAID just crashed.
So I may as well share it.... if I understand it correctly.......
It seems that it may have a similar weakness to the zip format.. if I'm not mistaken.
public override bool DecryptWithPassphrase(string passphrase){
.....}
If we look down we see:
byte[] checksum = sha256.ComputeHash(utf8.GetBytes(passphrase + "?"));
if (hex[2] != 0x80) {
if ((checksum[0] & 0x7f) != hex[2] || (checksum[1] & 0x7e) != (hex[3] & 0x7e)) {
return false;
}
}
It seems we can recover a partial solution, because if it is NOT a partial solution the above will fail.
By getting the products up-to this stage, popping them over the serial port to an fpga...... and since Bitcoin is DOUBLE sh256
We can get two engines cycling thrugh the Sha256 keys for the range AAAAA-zzzzz ( actually by splitting the space over two devices we can half the searchtime with a brute it becomes 190102016
Each time we get a 'hit' from the above, we pop it back to the computer to drop it into the code that follows the above code in "DecryptWithPassphrase"
so even with a XUPV5 I can get over 500MHS through the key address space
52*52*52*52*52=380204032
0.76 seconds Unless my maths have broken down.
Like I say my development env. crashed so I've nothing to test with.