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
I developed a simple patch for use on client proxmark3 the raw function already implemented in PM3 firmware.
So now we can use RAW 14a with LUA and also with command line.
You can download the patch from here http://www.sendspace.com/file/8213nl
I tried to do a better indentation code in armsrc/iso14443a.c but I see there is many works todo.
Maybe there is a little change not acceptable, I clear the trace only on connect and not for each call to ReaderIso14443a.
On client we can choose if send partial byte or full 8 bit, useful for command as REQA or Mifare Magic Chinese.
An example:
hf 14a raw -p -b 7 -a 26
hf 14a raw -p 93 20
hf 14a raw -p -c 93 70 16 15 CA 34 FF
hf 14a raw -p -c 60 00
proxmark3> hf 14a list
recorded activity:
ETU :rssi: who bytes
---------+----+----+-----------
+ 0: : 26
+ 236: 0: TAG 04 00
+ 0: : 93 20
+ 452: 0: TAG 16 15 CA 34 ff
+ 0: : 93 70 16 15 ca 34 ff e8 5c
+ 308: 0: TAG 08 b6 dd
+ 0: : 60 00 f5 7b
+ 428: 0: TAG 2c cc c3 58 There is also an option for use the function select on PM3
hf 14a raw -p -s -c 6000
proxmark3> hf 14a list
recorded activity:
ETU :rssi: who bytes
---------+----+----+-----------
+ 0: : 52
+ 236: 0: TAG 04 00
+ 0: : 93 20
+ 452: 0: TAG 16 15 CA 34 ff
+ 0: : 93 70 16 15 ca 34 ff e8 5c
+ 308: 0: TAG 08 b6 dd
+ 0: : 60 00 f5 7b
+ 428: 0: TAG 97 67 bc 11 Offline
L.O.V.E. !
It works great!
Hope that it will be implemented soon in the main trunk !
Last edited by asper (2013-09-24 20:00:06)
Offline
Good work, committed as of r784.
Just a minor thing; could you please try to not include changes to whitespace within functionality-patches? It's better to make a separate formatting-patches which does not do any functional difference, and when you implement or change functionality, have patches that contain only that. That makes it easier to verify the correctness of both types of patches. Oh, and dont forget to send your google-account details to roel for svn access...
Offline
could you please try to not include changes to whitespace within functionality-patches?
I will do, sorry for that.
Offline
Pages: 1