There are several cases. Packets are far apart in time (say over a second, while ideally should be slightly more then 0.05 seconds). Packets are near in time, but from different sessions. Roughly (without technical details) the router sends, for instanse, 50 requests with some mark (session's mark) and waits for a response. Next 50 requests it sends with other mark (other session). It was captured a request from one session (say number 50), and the response from the other (say number 1). The right responses were missed. Due to the session's marks do not match test with correct password will not be successful. Sometimes the packages may be slightly damaged, but programs don't see it. Need to open capfile by wireshark and choose good/another pair of packets, delete all others, save as another capfile and try it.
Hashcat exhausted, yet password is in dictionary
|
« Next Oldest | Next Newest »
|
Messages In This Thread |
Hashcat exhausted, yet password is in dictionary - by TheFool - 12-18-2016, 07:43 PM
RE: Hashcat exhausted, yet password is in dictionary - by atom - 12-18-2016, 11:31 PM
RE: Hashcat exhausted, yet password is in dictionary - by TheFool - 12-18-2016, 11:38 PM
RE: Hashcat exhausted, yet password is in dictionary - by PutNick - 12-18-2016, 11:51 PM
RE: Hashcat exhausted, yet password is in dictionary - by TheFool - 12-18-2016, 11:57 PM
RE: Hashcat exhausted, yet password is in dictionary - by PutNick - 12-19-2016, 12:09 AM
RE: Hashcat exhausted, yet password is in dictionary - by atom - 12-22-2016, 02:46 PM
|