#10 rainbow chain length verify fail

closed
None
5
2011-07-30
2009-10-04
James Nobis
No

From http://www.freerainbowtables.com/phpBB3/viewtopic.php?f=2&t=1392&start=0&hilit=table+verify+fail

ntlm_alpha-space#1-9_0_10000x67108864_disrrtgen[p][i]_00.rti:
reading index... 65462034 bytes read, disk access time: 0.06 s
reading table... 536870912 bytes read, disk access time: 0.54 s
verifying the file...
rainbow chain length verify fail

ntlm_alpha-space#1-9_0_10000x67108864_disrrtgen[p][i]_12.rti:
reading index... 62419203 bytes read, disk access time: 0.04 s
reading table... 234102304 bytes read, disk access time: 0.34 s
verifying the file...
rainbow chain length verify fail

ntlm_loweralpha-space#1-9_3_10000x67108864_disrrtgen[p][i]_02.rti:
reading index... 62420523 bytes read, disk access time: 0.04 s
reading table... 268115488 bytes read, disk access time: 0.25 s
verifying the file...
rainbow chain length verify fail

Discussion

  • Nobody/Anonymous

    I ran into this issue on Ubuntu 9.04 x86_64 running 0.6.3 with hybrid MD5 tables. After recompiling rcracki_mt as 32bit I no longer had an issue.

     
  • Nobody/Anonymous

    Using 2 threads for pre-calculation and false alarm checking...
    Found 1 rainbowtable files...

    md5_hybrid(loweralpha#7-7,numeric#1-3)#0-0_0_13000x67108864_distrrtgen[p][i]_00.rti:
    Debug: Saving 103992 bytes of memory for chainwalkset.
    Debug: Allocated 80575803 bytes for index with filelen 80575803
    Debug: Setting index to 0x00 in memory, 80575803 bytes
    reading index... 80575803 bytes read, disk access time: 0.05 s
    Debug: Allocated 536870912 bytes for 67108864 chains, filelen 536870912
    Debug: Setting pChain to 0x00 in memory
    reading table... 536870912 bytes read, disk access time: 0.33 s
    verifying the file... rainbow chain length verify fail
    Debug: writing progress to rcracki.progress

    Debug: Removing session files.

     
  • Nobody/Anonymous

    The original bug mentioned occurred on both 64bit and 32bit systems. You may have encountered a new bug. I'll see if I can duplicate it tonight.

     
  • James Nobis

    James Nobis - 2009-11-06

    The 2nd bug mentioned with hybrid tables was opened as a new bug with the subject: "64bit specific table verify fail." This bug has been fixed in my source but I need to do more testing before committing the fix. In any case the scope is limited to 64bit platforms and hybrid tables. This bug is completely unrelated to the bug in the description.

     
  • James Nobis

    James Nobis - 2011-07-30
    • status: open --> closed
     
  • James Nobis

    James Nobis - 2011-07-30

    ntlm_loweralpha-space#1-9 set was regenerated and is hosted on GARR as RTI2
    ntlm_alpha-space#1-9 set is currently being regenerated and then will be hosted on GARR as RTI2

    Both sets had actual invalid data files.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks