-Crypt8 Calculator2 added
you can now calculate B8hx00h, B8hxFFh and B8hx03000h crypt8 values for cw's given in a txt.file
_https://mega.nz/#!ps4DzQKR!I7yMG01DFq155aLSxnApc6MFEWGZ9JLJFEwhc4zEzL0
how does this software extract the key from rbt
-Crypt8 Calculator2 added
you can now calculate B8hx00h, B8hxFFh and B8hx03000h crypt8 values for cw's given in a txt.file
_https://mega.nz/#!ps4DzQKR!I7yMG01DFq155aLSxnApc6MFEWGZ9JLJFEwhc4zEzL0
Forgive my ignorance, are you saying that a single crypt 8 produced 3 keys?
Forgive my ignorance, are you saying that a single crypt 8 produced 3 keys?
No... a single CW produced 3 crypt8....00h,ffh,03h
The collision comes from the reduction from 8bytes to 6bytes during calculation of the chains. A reduction function is e.g. to omit the bytes 7 and 8. The collision is then obvious:Wao I realize I did make an error.
Well it is true that some crypt may produce Hash_collision and possibly CSA is one of them. This is effect is that a 2 different CW will SINGLE encrypt to same value. Now to be honest I never has seem that rear occurrence in CSA.
12 34 56 78 9A BC DE F0 => 12 34 56 78 9A BC
12 34 56 78 9A BC 10 54 => 12 34 56 78 9A BC
I guess, there is something mixed up:So if that chain do not loop or have imperfection like repeating a cw very fast.
Well then a CW in RBT V1 has 65536 cryptos. Yes a lots.
The collision comes from the reduction from 8bytes to 6bytes during calculation of the chains. A reduction function is e.g. to omit the bytes 7 and 8. The collision is then obvious:
Code:12 34 56 78 9A BC DE F0 => 12 34 56 78 9A BC 12 34 56 78 9A BC 10 54 => 12 34 56 78 9A BC
Crypt8 values for one single cw depend on the payload and the payload size and therefore you can have a lot more (~( 2^(184x8))x23 )
...and that's where the rainbow part comes in... after discarding the last two bytes, the truncated 12 34 56 78 9A BC values are XOR'd with the round number (or link position in chain). Only if the values occur at the *same link position / round number* do you have a merging of chains. If not, both chains continue to meander down different paths of C8->CW links, thanks to the rainbow element of the reduction function.
The collision comes from the reduction from 8bytes to 6bytes during calculation of the chains. A reduction function is e.g. to omit the bytes 7 and 8. The collision is then obvious:
Code:12 34 56 78 9A BC DE F0 => 12 34 56 78 9A BC 12 34 56 78 9A BC 10 54 => 12 34 56 78 9A BC
Correct me if I am wrong, but aren‘t we talking about different approaches?Only the first 8 bytes of the encrytped payload are crypt8 values... (the rest of the payload is further mangled with the stream cypher, not pure block cypher like the initial 8 bytes). So this ~( 2^(184x8))x23 figure makes no sense... the count of possible Crypt8s per plaintype_payload_length is exactly the same as the keyspace, 2^48. Or 2^48 x 23 for all possible lengths of one plaintype.
Sorry but collision must exist only in your head.
AC 91 46 29 C6 07 85 FA => 12 34 56 78 9A BC FFh table