4 ms·
Almost all of this is about a 2013 trial and not this present proceeding at all. And the claim (from that trial) is that Manning provided Assange with bytes fro
by tialaramex 6y ago
Almost all of this is about a 2013 trial and not this present proceeding at all. And the claim (from that trial) is that Manning provided Assange with bytes from an encrypted SAM or that it's only part of the password hash.
It's actually pretty aggravating reading trial documents when nobody present knows what they're talking about, it might as well be a Star Trek script, this is why it's so nice when the trial judge or at least some of the lawyers know what they're talking about (e.g. the Horizon scandal in the UK) but we can't have nice things most of the time.
Here's what the transcript says Manning provided:
80c11049faebf441d524fb3c4cd5351c
That's 16 bytes = 128 bits = one Windows password hash.
So straight away it's completely reasonable that this is in fact a Windows password hash, and in the absence of evidence of how Manning obtained that value it's only speculation that this is actually encrypted somehow (e.g. because it is from an encrypted offline SAM). And yet Assange's defence apparently has hours of such speculation on tap, for whatever they suppose that's worth.
What Assange talks about doing is using Rainbow tables. This would be applicable regardless of which type of Windows hash it is (or Assange thought it was) but crucially if the password is strong then you only get a result if this 128-bit value is an LM Hash. The risible LM Hash turns the first seven characters into one 64-bit value using DES, the next seven into another 64-bit value (DES again). It doesn't work on long passwords, if you have a long password then you can't have an LM hash. This of course is one reason somehow who tried to obtain both hashes would only get one...
The NT Hash is MD4(password). If the password is "qwerty" or "manning" that's not difficult to find, and Rainbow Tables that will be fairly reliable for simple passwords with NT Hash are readily available and would have been years ago too.
But if the password is sixteen random characters then MD4(password) might as well be Argon2id(password) for all the good that'll do you. It's just too many combinations.
So, for all we may ever know that 128-bit value is in fact a legitimate NT Hash of a good password.