Files
proxmark3/client
歐歪andClaude Opus 5 14a5de0bdf fix: let the device verdict decide the outcome of hf 15 csetuid
The client only inspected PM3_EWRONGANSWER and then re-verified with its own
getUID(), which asks whether the tag carries the requested UID, not whether
this command wrote it. Running csetuid --v3 twice with the same UID printed
"Setting new UID ( ok )" on the second run even when the device had reported
PM3_ESOFT, because the UID written by the first run still matched.

Gen1 and V3 now switch on the device status, which already covers tag
identification and UID verification. V2 keeps the client side comparison,
the device does neither for it. PM3_ETIMEOUT is handled as well, cfinalize
already did that.

The cfinalize help text and its confirmation warning said the configuration
area is erased. Finalize erases the whole tag memory to 00000000.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-22 21:08:18 +08:00
..
2026-08-27 22:37:59 +02:00
2026-09-16 19:00:50 +02:00
2026-09-14 12:40:51 +02:00
2026-08-26 16:07:37 +02:00
2025-09-02 16:16:29 +02:00