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.
So, my Proxmark3 reads my lf badge, and even writes it to my HID ProxCard II. Problem is the Prox Card II badge will not open the door. Here is a log of everything I did in the console:
root@kali:/corey/proxmark3/client# ./proxmark3 /dev/ttyACM0
(process:1850): GConf-WARNING **: 15:15:44.663: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(proxmark3:1850): GConf-WARNING **: 15:15:44.732: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Qt: Session management error: None of the authentication protocols specified are supported
Prox/RFID mark3 RFID instrument
bootrom: master/v3.0.1-397-gd62f7ba-suspect 2018-08-30 02:24:26
os: master/v3.0.1-397-gd62f7ba-suspect 2018-08-30 02:24:27
fpga_lf.bit built for 2s30vq100 on 2015/03/06 at 07:38:04
fpga_hf.bit built for 2s30vq100 on 2018/08/13 at 21:22:51
uC: AT91SAM7S256 Rev D
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 194796 bytes (74%). Free: 67348 bytes (26%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3> lf search
NOTE: some demods output possible binary
if it finds something that looks like a tag
False Positives ARE possible
Checking for known tags:
Securakey Tag Found--BitLen: 26, Card ID: 32946, FC: 0x16, Raw: 7FCB400000B4026536800000
Wiegand: 002D0165, Parity: Passed
How the FC translates to printed FC is unknown
How the checksum is calculated is unknown
Help the community identify this format further
by sharing your tag on the pm3 forum or with forum members
Valid Securakey ID Found!
proxmark3> lf hid clone 002D0165
Cloning tag with ID 0002d0165
#db# DONE!
proxmark3> lf search
NOTE: some demods output possible binary
if it finds something that looks like a tag
False Positives ARE possible
Checking for known tags:
HID Prox TAG ID: 0002d0165 (32946) - Format Len: 37 bits - FC: 2 - Card: 426162
Valid HID Prox ID Found!
proxmark3>
Offline
I just ran an 'lf search' on my RFID Tag, and then a 'lf hid clone'
It overwrote my RFID Tag with information, and now my real tag won't open the door either!
Offline
Probably not opening the door due to the door receiving the wrong card number? What ID is your door expecting?
Offline
Or the fact that a securakey is not an hid key.
Offline
Yes, but is there any support for securakey?
Offline
Or the fact that a securakey is not an hid key.
Oops I missed that! Lol
Offline