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
Hey,
I got a problem when using the command chk, it displays fo the keys '0000' in the 2 first bytes. But when doing a dump in a file I got the good keys.
Example : when using the chk command I got key = [0000ffffffff] and when dumping it in the bin file I got the good key [ffffffffff] what can be the problem with the first display ? and how can I fix it ?
Thanks !
Offline
Problem solved, for those who will got the same I advice them to go common folder then to the file cmdhfmf.c and then change all the printf that have %012llx to %012I64x.
Normaly after that, everything would work Hope I've helped out someone !
Offline
I had the same problem, when I do nested attacks the keys that been found always had '0000' in the beginning, and it was not the correct key.
Replacing all llx to I64x works well!
I suggest that someone changes all this occurrences in the official svn:
https://code.google.com/p/proxmark3/source/search?q=llx&origq=llx
Last edited by urkis (2013-01-10 23:04:38)
Offline
Yeah hope someone can fix it !!
Offline
I had the same problem, when I do nested attacks the keys that been found always had '0000' in the beginning, and it was not the correct key.
Replacing all llx to I64x works well!I suggest that someone changes all this occurrences in the official svn:
https://code.google.com/p/proxmark3/source/search?q=llx&origq=llx
Fixed in r649, please try out now.
Offline
urkis wrote:I had the same problem, when I do nested attacks the keys that been found always had '0000' in the beginning, and it was not the correct key.
Replacing all llx to I64x works well!I suggest that someone changes all this occurrences in the official svn:
https://code.google.com/p/proxmark3/source/search?q=llx&origq=llxFixed in r649, please try out now.
Fixed! Thanks!
Offline
Pages: 1