dwpa icon indicating copy to clipboard operation
dwpa copied to clipboard

Unfound since summer, just 8 digits

Open FFAMax opened this issue 1 year ago • 3 comments

Hey Alex. We have wps* and num8* dicts, they cover entire range 0000000-99999999, I didn't found missed numbers in the dicts, but recently found several submissions was coming regularly, like

2024-10-28 16:40:13 2024-10-18 19:10:47 2024-10-18 19:10:47 2024-09-19 04:25:06 2024-09-06 20:38:09 2024-09-04 20:07:47 2024-08-20 19:00:05 2024-08-20 19:00:05 2024-08-14 20:10:49 2024-08-14 19:24:32 2024-07-29 16:37:38 2024-07-27 19:06:19

and key was never found until now. Any ideas?

FFAMax avatar Nov 14 '24 13:11 FFAMax

Another one, hkey E501774E7422C1C2D50F65E2675F4EB8, the same

FFAMax avatar Nov 14 '24 13:11 FFAMax

We can hardly pass the full 8-digit keyspace. Most of the networks are tried against WPS pins at most, then we work on older networks. The algorithm is this: pull the current work unit, then if the cracking job finishes under 5 minutes, increment the dictionary count, up to 15 dicts, ordered by smaller to bigger ones. We also combine the same ESSID networks to do the heavy PBKDF2-SHA1-4096 just once. Some networks are cracked prematurely, when we try different approaches or keygens.

RealEnder avatar Feb 22 '25 10:02 RealEnder

Wanna make sure we are talking about the same. What I found - PSK was not found in several months. I'm sure it went through 14+ dicts during this time. What I think - somehow work was not finished. Not sure how it works: if helper got a work, and not PSK found, worker will report 'I tried this dict and no matches' or will just take next dict?

FFAMax avatar Mar 04 '25 06:03 FFAMax