The latest sourcecode is on GitHub, the latest official release is v3.0.1 and can be downloaded from there.
svn checkout http://proxmark3.googlecode.com/svn/trunk proxmark3
svn: E170013: Unable to connect to a repository at URL 'http://proxmark3.googlecode.com/svn/trunk'
svn: E160013: '/svn/trunk' path not found
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 754 2013-07-09 17:22:17
#db# os: svn 754-unclean 2013-07-10 01:32:53
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3> hf mf mifare
-------------------------------------------------------------------------
Executing command. It may take up to 30 min.
Press the key on the proxmark3 device to abort both proxmark3 and client.
-------------------------------------------------------------------------
Really weird.. the above output is using the proxmark3 client after compiling from source... but using the precompiled stuff from Asper & co. using the GauchGUI and the proxmark3.exe the stuff is running fine... I'm not pretty sure what's going on...
]]>Oh! Also, I'm compiling from source, and using the proxmark3.exe client I get:
proxmark3> hf mf mifare
-------------------------------------------------------------------------
Executing command. It may take up to 30 min.
Press the key on the proxmark3 device to abort both proxmark3 and client.
-------------------------------------------------------------------------
Do a 'hw version' with this client. I don't think it is really at r754. Compilation errors that you didn't notice perhaps?
]]>proxmark3> hf mf mifare
-------------------------------------------------------------------------
Executing command. It may take up to 30 min.
Press the key on the proxmark3 device to abort both proxmark3 and client.
-------------------------------------------------------------------------
but using the other client (Gaucho scripting one):
proxmark3> hf mf mifare
-------------------------------------------------------------------------
Executing command. Expected execution time: 25sec on average :-)
Press the key on the proxmark3 device to abort both proxmark3 and client.
-------------------------------------------------------------------------
What's going on here? Any ideas?
thanks!
]]>This behaviour is common right now?
Thanks.
]]>Fixed in r754.
]]>Right now, the 'example' usage in flasher is :
Example:
client/flasher path/to/osimage.elf path/to/fpgaimage.elf
I didn't remove that, but it looks like it's outdated. I added a linux-example:
Example (Linux):
client/flasher /dev/ttyACM0 armsrc/obj/fullimage.elf
Maybe you can find also this interesting (I was ablet o solve with a dirty code hack) but I don't know if it is really a bug or a normal mifare standard behaviour, the fact is that it is conflicting with the purpose of Chinese Changeable UID cards...
]]>I can tell you that the command (cgetsec or cgetblk) is going right to the card and also the answer to PM3 is correct (using LIST command after a command you can see data sent and received in the last transaction and it does not contains any 44, only the real good bytes !).
Knowing that can you make a guess on where the 44 "obfuscation" happens ? I need a patch but I am not so got at source code to make one this time...
// add trace trailer
memset(uid, 0x44, 4);
LogTrace(uid, 4, 0, 0, TRUE);
LED_B_ON();
cmd_send(CMD_ACK,isOK,0,0,uid,4);