mirror of
https://github.com/RfidResearchGroup/proxmark3.git
synced 2026-11-14 11:48:45 +00:00
iceman1001andClaude Opus 5.5
1f543f3ced
The retry check estimated the next attempt from the longest one so far. That does not bound it: - get_pulse_length() waits up to 4 bit periods - one find_double_listen_window() can take about 3.2 s with no signal - a login + read attempt can take over 6 s - setup before tstart was not counted A slow attempt after fast failures could end after the client gave up, leaving the late reply queued for the next command. read and info now set a deadline after setup, 1 s before the client timeout. The listen window, ACK and word decode loops stop at the deadline, as do the retries. With no deadline set (write, brute, sim, ...) they behave as before. The client waits 5 s for read, as it already did for info / dump. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>