From 9c05f2c729dc9ec896e70263cf09cdf4542d1f94 Mon Sep 17 00:00:00 2001
From: Philippe Teuwen <phil@teuwen.org>
Date: Thu, 16 Jan 2025 22:43:35 +0100
Subject: [PATCH] hf mfu info: fix strong mod bit parsing

"2" was probably referring to bit 2 == 0x04
I checked the following datasheets and STRG_MOD_EN is always at 0x04:
- UL EV1
- NTAG 213/215/216
- NTAG 213_F/216_F
---
 client/src/cmdhfmfu.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/client/src/cmdhfmfu.c b/client/src/cmdhfmfu.c
index 71c8b76f8..1fe6a5cd0 100644
--- a/client/src/cmdhfmfu.c
+++ b/client/src/cmdhfmfu.c
@@ -1142,8 +1142,7 @@ static int ulev1_print_configuration(uint64_t tagtype, uint8_t *data, uint8_t st
     PrintAndLogEx(NORMAL, "");
     PrintAndLogEx(INFO, "--- " _CYAN_("Tag Configuration"));
 
-    bool strg_mod_en = (data[0] & 2);
-
+    bool strg_mod_en = (data[0] & 0x04);
     uint8_t authlim = (data[4] & 0x07);
     bool nfc_cnf_prot_pwd = ((data[4] & 0x08) == 0x08);
     bool nfc_cnf_en  = ((data[4] & 0x10) == 0x10);