V1 tables search code in CSA Rainbow Table Tool far from perfect. You can drastically improve speed by rewriting software.
As we know Colibri stop coding it few years ago unfortunately , otherwise you have some new ideas to apply .
V1 tables search code in CSA Rainbow Table Tool far from perfect. You can drastically improve speed by rewriting software.
BLACKCRUSADER
V1 tables search code in CSA Rainbow Table Tool far from perfect. You can drastically improve speed by rewriting software.
And the thread is not really about that,do we agree?
I mean,you could have been a great help 4 years ago,he he.....
Some people missed the boat,but hey knew they could have swam faster than the boat........a boat that already made the trip 100 times
I agree,what i see it as the best card gets keys in a minute and a half,how lower can we get? 60 seconds?kebien
I don't get it. I thought that V1 tables still very useful.
And there's source code available for CSA Rainbow Table Tool (old version, but major stuff is there).
We are looking for that and waiting your perfect work such as CWBruteList 1.0.0.17 :thum:kebien
More like down to 6..40 seconds (depends on "luck").
kebien
More like down to 6..40 seconds (depends on "luck").
Thanks for posting your timings: it was my inspiration to seek & find better algorithms... all the same I needed a hardware upgrade to 1070ti to get somewhere close.kebien
More like down to 6..40 seconds (depends on "luck").
Using table D:\CSA_B8hxFFh_10000h.rbt, 28.454 billion chains. End6 range 000000005DD0h-FFFFFFFFAADFh.
Searching rainbow table for C8: F6 A2 3E 1D 91 36 32 BA, range 2000h links per round.
2.8s: 2000h end6 values calculated, commencing disk search E000h-FFFFh
6.3s: 3590 chains found. Rebuild using 8 grids @ 15 x 256 threads needed for max link FE96h:
RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link F04Ch
RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link F04Ch
9.9s: 10304 chains found. Rebuild using 7 grids @ 41 x 256 threads needed for max link DFF7h:
RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link C396h
15.5s: 17578 chains found. Rebuild using 6 grids @ 69 x 256 threads needed for max link BFFDh:
RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link BD3Bh
RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link BD3Bh
20.0s: 23806 chains found. Rebuild using 5 grids @ 93 x 256 threads needed for max link 9FFFh:
25.6s: 30272 chains found. Rebuild using 4 grids @ 119 x 256 threads needed for max link 7FFBh:
31.1s: 36734 chains found. Rebuild using 3 grids @ 144 x 256 threads needed for max link 5FFEh:
35.0s: 44100 chains found. Rebuild using 2 grids @ 173 x 256 threads needed for max link 3FFEh:
38.7s: 50688 chains found. Rebuild using 1 grids @ 198 x 256 threads needed for max link 1FFEh:
RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link 047Dh
Found CW: FD 41 5A 98 B7 8A FF 40
All end6s calculated in 11.5s, 217072 start6s fetched in 29.2s, all chains rebuilt in 28.8s. Total 39.7s
Thanks for posting your timings: it was my inspiration to seek & find better algorithms... all the same I needed a hardware upgrade to 1070ti to get somewhere close.
Blackcrusader's search of v1's public tables B8hxFFh (1 & 2 merged) from earlier in this thread is repeated here:
Blackcrusader has a stunningly fast SSD: using the Colibri tools here gives 4x slower performance cf what reported.Code:Using table D:\CSA_B8hxFFh_10000h.rbt, 28.454 billion chains. End6 range 000000005DD0h-FFFFFFFFAADFh. Searching rainbow table for C8: F6 A2 3E 1D 91 36 32 BA, range 2000h links per round. 2.8s: 2000h end6 values calculated, commencing disk search E000h-FFFFh 6.3s: 3590 chains found. Rebuild using 8 grids @ 15 x 256 threads needed for max link FE96h: RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link F04Ch RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link F04Ch 9.9s: 10304 chains found. Rebuild using 7 grids @ 41 x 256 threads needed for max link DFF7h: RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link C396h 15.5s: 17578 chains found. Rebuild using 6 grids @ 69 x 256 threads needed for max link BFFDh: RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link BD3Bh RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link BD3Bh 20.0s: 23806 chains found. Rebuild using 5 grids @ 93 x 256 threads needed for max link 9FFFh: 25.6s: 30272 chains found. Rebuild using 4 grids @ 119 x 256 threads needed for max link 7FFBh: 31.1s: 36734 chains found. Rebuild using 3 grids @ 144 x 256 threads needed for max link 5FFEh: 35.0s: 44100 chains found. Rebuild using 2 grids @ 173 x 256 threads needed for max link 3FFEh: 38.7s: 50688 chains found. Rebuild using 1 grids @ 198 x 256 threads needed for max link 1FFEh: RBTv1 kernel B8hxFFh hit using CW: FD 41 5A 98 B7 8A FF 40 @ link 047Dh Found CW: FD 41 5A 98 B7 8A FF 40 All end6s calculated in 11.5s, 217072 start6s fetched in 29.2s, all chains rebuilt in 28.8s. Total 39.7s
With blackcrusader's SSD & your GPU, a v1 search might be done in 20secs (compute bound).
And yes, I am missing a handful of found chains v Colibri/Blackcrusader's count, to be investigated.
Samsung 970 EVO Plus PCIe NVMe M.2 should yeild a decent performance boost over an old school sata 3 ssd. Those sammy evo's are a decent price to.
a fast gpu was important for the creating of chains.
for searching cw's a faster ssd paired with a low end gpu will be faster than a slow ssd with high end gpu imo.
40 secs is consistent on that sized table to perform an exhaustive search of every candidate chain. That is tables 1&2 merged into one big table as Blackcrusader has. Of course I could've chosen to stop on the first hit, in this case around 8 seconds.
Fully searching table1 or table2 separately without merging takes around 30 seconds each with my hardware, again with the first hit no sooner than 6 seconds, depending on luck.