Using PACK - Interesting Results - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Misc (https://hashcat.net/forum/forum-15.html) +--- Forum: General Talk (https://hashcat.net/forum/forum-33.html) +--- Thread: Using PACK - Interesting Results (/thread-7067.html) |
Using PACK - Interesting Results - walterlacka - 12-01-2017 New to using PACK so maybe using it incorrectly.. here's what I'm seeing: Code: python policygen.py --minlength=9 --maxlength=9 --mindigit=1 --maxdigit=3 --minspecial=1 --maxspecial=2 --minupper=1 --maxupper=2 --minlower=1 --maxlower=6 Even though I specify maxdigit=3, in the Max Strength section above, it still says d:None If I do the following: Code: python policygen.py --minlength=9 --maxlength=9 --mindigit=1 --maxdigit=8 --minlower=1 No matter what I do with maxdigit, it doesn't get recognized... I was thinking it was cosmetic so I ran the same command but output it to a file, and sure enough there were extra ?d in the mask lists. Am I using this incorrectly? I'm trying to create a mask file that has: exactly 9 length min 1 special max 2 special min 1 upper max 2 upper min 1 digit max 3 digit min 1 lower max 6 lower (since 1 upper 1 special 1 digit is min - that would make 9) RE: Using PACK - Interesting Results - philsmd - 12-01-2017 This problem was already reported several months ago (see https://github.com/iphelix/pack/issues/1), but it wasn't merged yet. I think there are some forked versions that integrate the fix, like the python 3 version of @hydraze https://github.com/Hydraze/pack You could just make the slight change recommended in the issue and everything should work fine or try to use a newer fork (but I'm not sure what other changes they made to the project etc... I only know that the one from hydraze should be run with python3, which shouldn't be a problem at all). RE: Using PACK - Interesting Results - walterlacka - 12-01-2017 That worked. Thanks philsmd. RE: Using PACK - Interesting Results - walterlacka - 12-02-2017 Now I've got myself thoroughly confused.. I ran the following (using the fix that philsmd pointed me to): Code: [*]Using 12,000,000,000 keys/sec for calculations. Notice it was 9 for min/max length Lower 1/9 Upper 0/1 Digit 0/4 Special 0/2 Created 28246 policy masks Then I ran the following: Code: [*]Using 12,000,000,000 keys/sec for calculations. Everything same as first run EXCEPT in this case I'm using Min/Max 2 for UPPER (I've also changed the max for lower to be 7 since min upper is 2). This created 41364 policy masks. As a quick "logic-check", I ran the following next: Code: [*]Using 12,000,000,000 keys/sec for calculations. This one is basically the "combination" of the two examples above - it has same MIN/MAX for digit and special. But for upper it has 0/2 min/max. All three example using 9 for mask length. Notice that number of policy masks from example 1 and 2 add up to the number of policy masks in example 3. So at quick glance I thought my logic was solid.... but then I started thinking about it more and.. I can't figure out why the second example created more policy masks than the first example. In the first example, it was trying 0 or 1 UPPER. In the second example, it was trying EXACTLY 2 UPPER (which in my mind means less policy masks). EDIT:after thinking about this more, I'm guessing the reason for this is that with 2 UPPER's, they have 9 different places they could go in the mask - is this right? |