Proxmark developers community

Research, development and trades concerning the powerful Proxmark3 device!

You are not logged in.

#2 Re: Questions and Requests » Do you recognise these types, are they RFIDs .... » 2016-04-14 07:53:14

They seems to be programmable UHF remote controls, you cannot use pm3 for them.

They usually comes in 3 frequencies: 315, 433.92 and 868.3 MHz but the most common one is 433MHz (you can open it and look at the internal oscillator frequency to be sure).

You need to know how to program them; usually you need to hold 1 or 2 buttons at the same time to "erase" the memory and then keep pressed a button while at the same time pressing the button you want to clone in the originale remote.

You can "analyze" them if you have something like this.

#5 Re: Proxmark Board Innovations » New PM3 with newer chip? » 2016-03-05 23:53:36

What do you think about an hackrf implementation/expansion ?

#6 Re: Proxmark Board Innovations » New PM3 with newer chip? » 2016-02-19 16:51:30

I will be interested!
Kickstarter campaign?

#7 Re: MIFARE Classic » A popular toy, Disney Infinity » 2016-02-16 13:26:09

junglipar wrote:
iceman wrote:

hm, did you change your DI base firmware?!? or do you call it with one of those node.js-usb projects I've seen and tested on Lego?

No. The DI firmware (STM32F102) calculates the key and gives it to the NFC frontend (MFRC630) which handles the MIFARE authentication. I simply attached my own microcontroller (STM32F103) to the SPI bus and wrote a small program that outputs the key via UART.

Very good P.O.C. ! Did you test some STM32F vulnerabilities ? If so can you share them even if they won't work with DI base ?

#10 Re: Questions and Requests » Is it possible to hack a SKIPASS ? » 2015-12-23 09:29:36

Wrong place, wrong subject and wrong way to ask. Go study before asking those idiot questions.

#11 Re: Questions and Requests » Unknown 13.56MHz tag in toy, not found by hf search, suggestions? » 2015-12-14 15:56:30

It is not ISO standard, probably a simple modulated 13.56MHz interface. You will need an oscilloscope or maybe the new pm3 function but i never used that because it is too recent.

#12 Re: Questions and Requests » Unknown 13.56MHz tag in toy, not found by hf search, suggestions? » 2015-12-09 17:21:57

Do you see a voltage drop before and after positioning the toy over the antenna ? Can you show it ?

#13 Re: MIFARE Ultralight » [FINISHED] a popular toy Lego Dimensions » 2015-12-03 12:21:07

Great sim ! Can you start with 00000000000000 and not 0400000000000 ? Thank you for your support !

#14 Re: MIFARE Ultralight » [FINISHED] a popular toy Lego Dimensions » 2015-12-01 12:52:06

It probably uses a pseudorandom generation algo; collectiong UIDs from ...00000, 00001, 00002, 00003 and correspective password is the only way to try to find it.

#15 Re: MIFARE DESFire » Desfire uid magic card? » 2015-11-26 14:14:03

Icode1 is NOT ISO15693-standard compatible !
I think it will not be the right product for uid-changing purpose.

#16 Re: Questions and Requests » [14b] Trying to read data from card » 2015-11-21 22:56:12

It probably uses Calypso standard (often used in transport systems) which is proprietary and actually undisclosed to public (for what know you need to be a transport service provider and you must pay to have it). If you want to study/reversing it you need to know the command set; you can get some info sniffing transaction but it will be an hard work.

#17 Re: Questions and Requests » [14b] Trying to read data from card » 2015-11-21 00:08:22

Ok, so you can try starting the software, put the card in the reader and show the ATR (I suggest you Smart Card Toolset Pro).

#18 Re: Questions and Requests » [14b] Trying to read data from card » 2015-11-19 19:28:52

Do you have a software to send APDUs like Smart Card Toolset Pro ?

#19 Re: Questions and Requests » [14b] Trying to read data from card » 2015-11-19 12:25:15

It seems to be a dual interface smartcard and the data you sniffed are (or seem to be) a smartcard apdu communication transaction (commands that can be send via contact interface embedded inside a rfid commandset); it is good that you managed to sniff.

You should try to sniff the very beginning of the transaction and see if the byte "E0" comes out.

If you have a smartcart (contact!) reader I can give you some commands to be tested.

#20 Re: Windows Client » Compiled Windows Client - Download » 2015-11-19 12:07:31

Added the new rev 2.5.0 to the 1st post.

#21 Re: Windows Client » [ERROR] Compiling Android Client in NDK » 2015-11-18 23:53:12

You don't read threads. Marcv81 code is extremely old, me and jonor managed To port it To a more recent release. This project offer NO support as stated in the 1st page proxdroid thread.

If Simeone want To contributo feel free To help but you are on tour own.

#22 Re: Windows Client » Compiled Android Client - Download » 2015-11-18 22:59:04

Again, this thread is NOT for support, please stop asking help here, just open another thread.

#24 Re: Windows Client » Compiled Android Client - Download » 2015-11-15 16:40:53

You need the correct compiled file for your exact kernel, other versions will not work. You need To compile it yourself if you are not able To find Someone who already compiled it.
Do not try the ones contained in my packet with a kernel different from the ones tested, they will not work.

#25 Re: Questions and Requests » inhova/tesa mifare password » 2015-11-14 14:59:00

4th, 5th and 6th bytes are related to 1st 3bytes values. Not at home To study it further today.

Board footer

Powered by FluxBB