A city asks whether mishandled EAPOL message order or incomplete frames can produce false 'bad handshake' errors in cracking tools. What process guidance is best?

Mishandled EAPOL message order or incomplete frames frequently produce tool failures or bad-handshake outcomes; the correct first fix is often recapture rather than assuming the cracker or wordlist is broken. Municipal assessors should treat capture integrity as a first-class variable. Corrupted or partial exchanges waste GPU budgets and generate false conclusions about passphrase strength.

'Bad-handshake errors always mean the passphrase is wrong, so expand the wordlist immediately.' fails because bad-handshake errors do not always mean the passphrase is wrong—fix the capture before expanding lists. 'Tool errors prove WPA2 is online-only and offline cracking must be abandoned forever.' fails because tool errors do not prove WPA2 is online-only or that offline cracking must be abandoned forever. 'Message-order issues only occur on WPA3-SAE and never on WPA2-PSK captures.' fails because message-order issues are not exclusive to WPA3-SAE; WPA2-PSK captures can be incomplete too.

Exam caveat: tool error messages are symptoms—validate frames before rewriting the entire dictionary strategy. Operational check: when the civic cracker rejects a file, re-open the capture, confirm EAPOL completeness and BSSID targeting, recapture during an authorized client join if needed, and only then resume offline testing. Document recapture events so report timelines stay accurate. In municipal wireless operations, record the rationale in the engagement notes so future assessors know which control or technique class was chosen and which failure modes the rejected options would create for city services.