4 ms·

As I was looking around for the files to make this project, on SecLists, Weakpass, and Hashes.org, most of the files were in alphabetical order. This was especi

• jacquesm 9y ago
  Yes, but it doesn't matter what order they are in if you put them in a DB. I don't know anybody that would do a sequential scan over a file in production. All you've done is shuffled around the most frequent cases to the beginning, which is great if that's what you are looking for, but now something else occupies the last slot and that case is just as bad as before. The real solution is to see these files as input to an indexed table so that you can get to the entry you want in log(n) time.
  • neuroid 9y ago
    I don't know anybody that would do a sequential scan over a file in production Well, that's pretty much how one would try to crack a password using a wordlist. EDIT: If the goal is to crack a bunch of properly hashed (PBKDF2, scrypt, etc.) and salted passwords then a lookup table is not very practical.
    • jacquesm 9y ago
      If you're trying to crack 'a password' you're doing it wrong. Alternatively, you're doing something illegal. That's not why these lists are made public (though I can appreciate the fact that they are 'dual use').
    • edoceo 9y ago
      PP is talking about a lookup, you are talking about cracking. Different things. For lookup of a string match make an index.