Files
proxmark3/client
Travis Weathers cce14d43e3 fix(client): stop the Indala demod printing a debug line at INFO level
detectindala() reports the bit count it gave up on through
PrintAndLogEx(INFO, ...), so every failed Indala demodulation prints

  [=] DEBUG: detectindala | 56

in normal output. It is the failure path: found_size < 64 means the
demodulator did not find a valid Indala (64 or 224 bits) and is returning
-5. Any noisy LF read hits it, so `lf search` with no card on the antenna
shows a developer's debug line to every user.

Every sibling in the same function already uses DEBUG, including the one
nine lines above it at "DEBUG: Warning - Indala had to invert bits", so
this is an oversight rather than a deliberate level. ui.c drops DEBUG when
g_debugMode is 0, which is the default, so the line stays available under
`data setdebugmode -1` and is simply no longer in the way.

Checked the whole client for the same class: the only other "DEBUG"
strings printed above DEBUG level are cmddata.c FSKToNRZ, and both of
those are already wrapped in `if (g_debugMode > 1)`, so they are correct
and are left alone.

Before, `lf search` over a reader field with no card:

  [=] Checking for known tags...
  [=] DEBUG: detectindala | 56
  [-] No known 125/134 kHz tags found!

After:

  [=] Checking for known tags...
  [-] No known 125/134 kHz tags found!

and with `data setdebugmode -1` the detectindala lines come back, now
carrying the [#] debug prefix like the rest of them.

Passes `make style` unmodified.
2026-09-15 10:57:02 -04:00
..
2026-08-29 17:42:29 +02:00
2026-08-27 22:37:59 +02:00
2026-09-14 12:40:51 +02:00
2026-08-26 16:07:37 +02:00