"Exploiting a SHA1 weakness in password cracking" *NOT* a weakness, a standard optimization http://heim.ifi.uio.no/hennikl/passwords12/www_docs/Jens_Steube_Passwords12.pdf … #FUD
-
-
@taviso Yes, it's a trade-off between otherwise optimal search order and raw candidate passwords/second speedThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@taviso Usually I prefer optimal search order, but in some cases a user might in fact want to resolve the trade-off in favor of raw speedThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@taviso For example, it is sometimes useful to exhaustively search and exclude an easily defined sub-keyspace (e.g., low lengths)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@taviso In terms of implementation for JtR, I think this could fit in with the set_mask() format method planned for fast hashes on GPUThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@taviso ... and we could do it on CPU too, indeedThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.