Practical PRINCE: 1 CPU + 24 hours = 63% Linkedin hashes cracked, 100% automated - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat-utils, maskprocessor, statsprocessor, md5stress, wikistrip (https://hashcat.net/forum/forum-28.html) +--- Thread: Practical PRINCE: 1 CPU + 24 hours = 63% Linkedin hashes cracked, 100% automated (/thread-3914.html) |
RE: Practical PRINCE: 1 CPU + 24 hours = 63% Linkedin hashes cracked, 100% automated - justme - 02-04-2015 I wonder now how duplicates are handled in prince? For example, for a 4 char keyspace we have: abc+d == ab+cd == a+bcd, etc. RE: Practical PRINCE: 1 CPU + 24 hours = 63% Linkedin hashes cracked, 100% automated - atom - 02-05-2015 (02-04-2015, 05:42 PM)justme Wrote: I wonder now how duplicates are handled in prince? For example, for a 4 char keyspace we have: abc+d == ab+cd == a+bcd, etc. Note that prince is not automatically brute-force. It needs to have a wordlist that contains such 1-letter words to make it one. Still, there are dupes generated. Prince can not handle those cases without loosing so much speed that it would not make any sense anymore. However if you use prince as it is suggested (using an ordered real-life wordlist) those are extremely rare. Here are some numbers, you can reproduce at home: Quote:root@et:~/princeprocessor/src# head -1000 /root/dict/untouched/rockyou.txt | ./pp64.bin | wc -l In other words, only 1/1710 is a dupe. RE: Practical PRINCE: 1 CPU + 24 hours = 63% Linkedin hashes cracked, 100% automated - ALDOKHM - 10-24-2017 (12-26-2014, 05:54 AM)rsberzerker Wrote: Great tutorial. It would be better IMHO if you included two things:[/quote] Is it possible to have more information on how filters are expressed when using the princeprocessor? I am trying to use princeprocessor to extract passwords from rockyou.txt that follow a particular pattern such as length, position of lower case, upper case, etc. Thanks |