Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
block# | data |lck| ascii
---------+--------------+---+----------
0/0x00 | 2F 28 E6 2B | 0 | /(.+
1/0x01 | D4 F3 B2 76 | 0 | ...v
2/0x02 | 98 7D 3E 2B | 0 | .}>+
3/0x03 | 9D 5F 7B CF | 0 | ._{.
4/0x04 | 4E 8E FE 92 | 0 | N...
5/0x05 | 05 9D 99 AC | 0 | ....
6/0x06 | 29 55 96 1E | 0 | )U..
7/0x07 | D7 CB F5 98 | 0 | ....
8/0x08 | 44 56 09 26 | 0 | DV.&
9/0x09 | 3F C1 07 E0 | 0 | ?...
10/0x0A | 00 00 00 00 | 0 | ....This was the dump from a tagit iso 15693 lable. Findafi gave me
[#] NoAFI UID = E0 07 C1 3F 26 09 56 44
[#] AFI = 0 UID = E0 07 C1 3F 26 09 56 44
[#] AFI Bruteforcing done.Here are my questions
1) is the venor encoding the data prior to putting it in the rfid chip, or is chip encoding the data?
2) if its the latter, is there a utility that can decipher the encoding
3) if its the former, does anyone have a sense of what was used to encode it or a workflow to decode it.
Thanks,
Offline
Pages: 1