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.
Hi,
I need to generate new VALID cards HID for a reader.
I have tested with this
if hid clone 2006ec0e73 and the card is generated, but it is not recognized for a reader.
#db# TAG ID: 2006ec0e73 (1849) - Format Len: 26bit - FC: 118 - Card: 1849
so I try to change the hex
lf hid clone 2006ec0e72
#db# TAG ID: 2006ec0e72 (1849) - Format Len: 26bit - FC: 118 - Card: 1849
Same FC and same ID...
And it works... So there must be a way to generate new ID cards.
Can anyone help me with this?
Offline
You need to calculate the checksum and set those bits accordingly.
Offline
Yes, I have seen the odd parity bit is wrong. Therefore I was looking for a generator.
Example write FC and ID and give the hex number for proxmark.
Offline
26bit - FC: 118 - Card: 1849
there is a beautiful document about wiegand 26bit I would recommend you to google.
You have missed a treasure, posted some weeks ago
"I have uploaded my latest version of the proxmark3 GUI by Gaucho and other good tools here: http://www.icedev.se/pm3.aspx"
Last edited by ntk (2017-05-06 10:02:52)
Offline
What type of generator are you looking for? Online like http://www.ccdesignworks.com/wiegand_calc.htm , command line written in Python or something, some sort of GUI, or ????
Offline
Thank you!!! this is exactly what i was looking for!
I just need add the 2006 to the value from this calculator!!
Data in HEX for this calculator 2EC0E72 and HEX for Proxmark 2006ec0e72.
I need to generate about 500 new cards.. so check one by one is a bit tedious
Thank you very much.
Offline
Technically you need to add 2004 to the calculated value, with the 4 getting added to the uppermost hex digit. I.E. if the calculator gives you 2EC0E72, you add 2004 = 2006EC0E72
Offline
There are generators, many people have written them. It is very good to study to understand Wiegand format. I would recommend study the PDF doc and following the calculation
Sometimes ago I worked on one. But I can niot help you now.
I found with shock I forgot the password and in other older document with no password protection, after changing laptop, and reinstall OpenOffice, files contains macros can be opened only with "DISABLING MACROS"
Does someone know the cure???
Offline
There is a lua script for the pm3 that works for bulk programming std 26 bit.
Offline
@Marshmellow, I think the OP wants to produce for the building FC=118, 500 cards with diiferent card ID from 1849 to 2349. The Lua script you say it can produce copy of the same FC and card ID only is it right
Last edited by ntk (2017-05-07 01:56:52)
Offline
Reading your post #1 I can not follow your thought where you get the 2EC0E73 from, in order to do your test whether "lf hid clone 2EC0E73" makes a good clone or not. That number does not come from the Wiegand logic.
///// FC=118 CrdID=1848
lf t55xx wr b 0 d 00107060
lf t55xx wr b 1 d 1D555955
lf t55xx wr b 2 d 5569A9A5
lf t55xx wr b 3 d 55A96A56
Wiegand raw data 2EC0E71
///// FC=118 CrdID=1849
lf t55xx wr b 0 d 00107060
lf t55xx wr b 1 d 1D555955
lf t55xx wr b 2 d 5569A9A5
lf t55xx wr b 3 d 55A96A59
Wiegand raw data 2EC0E72
///// FC=118 CrdID=1850
lf t55xx wr b 0 d 00107060
lf t55xx wr b 1 d 1D555955
lf t55xx wr b 2 d 5569A9A5
lf t55xx wr b 3 d 55A96A65
Wiegand raw data 2EC0E74
///// FC=118 CrdID=2348
lf t55xx wr b 0 d 00107060
lf t55xx wr b 1 d 1D555955
lf t55xx wr b 2 d 5569A9A5
lf t55xx wr b 3 d 56596695
Wiegand raw data 2EC1258
///// FC=118 CrdID=2349
lf t55xx wr b 0 d 00107060
lf t55xx wr b 1 d 1D555955
lf t55xx wr b 2 d 5569A9A5
lf t55xx wr b 3 d 5659669A
Wiegand raw data 2EC125B
Offline
Reading your post #1 I can not follow your thought where you get the 2EC0E73 from, in order to do your test whether "lf hid clone 2EC0E73" makes a good clone or not. That number does not come from the Wiegand logic.
///// FC=118 CrdID=1848
Wiegand raw data 2EC125B
Since I had not idea how HID hex number is generated I just incremented this number and test. Proxmark hasn't told anything about error. But the card didnt work on the reader.
The lua script is available to download? It would resolve my problem.
Offline
The lua script is available to download? It would resolve my problem.
It is in the latest code on github.
Offline
drakospart wrote:The lua script is available to download? It would resolve my problem.
It is in the latest code on github.
Thank you! i will give it a try! Last time i tried to install new software i made a strange mix that proxmark didn't work properly.
Offline
Use same client & fullimage from the same compilation. The rule is never mix between them. if you mix, you will get problems sooner or later.
Offline
Yes, Iceman, the main problem is that I have windows and I don't know how to compile the sources. Would be nice for newbies as me to have a link with the client and full image in a zip file for example. then never would make such mix
Offline
There is no problem at all, thanks to other forum users. Everything you need is posted, talked about and referenced here on the forum.
Search and you will find.
Offline
there is still some mistery on the FC code generation.
For example I want to make a card FC=136 and CARD#=17054
If i use the calculator http://www.ccdesignworks.com/wiegand_calc.htm i get as result 310853D
So after lf hid clone 2004310853D and write the card, make a fskdemod 1 and get this
#db# TAG ID: 2004310853d (17054) - Format Len: 37bit - FC: 1073 - Card: 17054 ... Why 37 bit? and also wrong FC?
The card number is Ok, but FC is wrong.
If I check the hex number in this https://www.brivo.com/support/card-calculator it says it is a 26bit FC=136 CARD#= 17054
Offline
I have got it using the 44 bit from this http://i.imgur.com/gPMUnay.png
proxmark3> lf hid clone 200710853D
Cloning tag with ID 200710853d
#db# DONE!
proxmark3> lf hid fskdemod 1
#db# TAG ID: 200710853d (17054) - Format Len: 26bit - FC: 136 - Card: 17054
Offline
Like I said above, you need to add the 4 from 2004 to the topmost digit. Given 310853D, 4 + 3 = 7, so 310853D -> 200710853D
Offline