Hopefully progress is finally getting close to being able to clone these? Any ETA on time to clone a specific SN w/o the card in-hand?
]]>Nice!
The general recommendation is to collect as much data you can. We never know when it might get in handy when trying to figure things out.
Here's tag no. 13412 with FC A6. The FC is read as 006 when using the *82 function on the Doorking 1837 system it is attached to. Also, FC F3 shows up as 053 on this system. Given that current Proxmark firmware shows up with 0x35 as the FC, I believe the FC's digits need to be reversed? May be wrong on that. FC 10/11 still don't make sense. Perhaps I'll also take them to this system if I get a chance.
]]>Nice!
The general recommendation is to collect as much data you can. We never know when it might get in handy when trying to figure things out.
What I meant by that post is how would I be able to write a given SN? FC isn't really needed as Linear's system doesn't check for FC unless it's been manually turned on.
]]>Nice!
The general recommendation is to collect as much data you can. We never know when it might get in handy when trying to figure things out.
How many more samples would it take to get something implemented where tags can be written bassed on SN/FC?
]]>The general recommendation is to collect as much data you can. We never know when it might get in handy when trying to figure things out.
]]>Its more a question of running the same commands over each cards, to gather the needed data and paste in the interesting data parts into a text file and putting the saved datatraces in a folder. No hi-tech.
lf securakey read lf read --replace UID with found fc/csn data save UID.pm3
Here's the traces: https://uploadfiles.io/wzul1 These tags are in Linear's ACT-31D transmitters.
I may be able to get access to another SecuraKey RCKM-02 tag with another facility code on it tomorrow. Also, I have several IDteck (Doorking branded) tags if any info from those would be of use.
]]>lf securakey read
lf read
--replace UID with found fc/csn
data save UID.pm3
atyppo wrote:marshmellow wrote:when you say FC is 11 and FC is 10, is that what is printed on the card or what is read by the access control system?
It is what is read by a Linear AM-DPR card reader (manufacturered by SecuraKey I believe) using Linear AccessBase software. These are embedded tags in a gate opener.
i assume you don't have these physical tags or don't know what was printed on them then?
i'm still not sure how the "Code" or Facility code printed on the card is related to the internal FC (if it is at all).
I have them in-hand
]]>marshmellow wrote:when you say FC is 11 and FC is 10, is that what is printed on the card or what is read by the access control system?
It is what is read by a Linear AM-DPR card reader (manufacturered by SecuraKey I believe) using Linear AccessBase software. These are embedded tags in a gate opener.
i assume you don't have these physical tags or don't know what was printed on them then?
i'm still not sure how the "Code" or Facility code printed on the card is related to the internal FC (if it is at all).
]]>yup, true, @atyppo has not posted any info on printed details. That would be nice to have a list of read data, tracesample file and printed information in a nice clean neat list. One could wish for less but why?
If I knew how, I'd be happy to
]]>when you say FC is 11 and FC is 10, is that what is printed on the card or what is read by the access control system?
It is what is read by a Linear AM-DPR card reader (manufacturered by SecuraKey I believe) using Linear AccessBase software. These are embedded tags in a gate opener.
]]>