Note that this information is incomplete at best, and possibly incorrect. It is purely what I’ve gleaned from observation and subsequent web-searching. Your actions are your own responsibility.
Reading RFID cards with the Proxmark is probably the most common use-case; it’s certainly the thing I do most often, followed by attempting to write the info onto a cloned card to verify that I’ve read all of the relevant info from the card.
The first thing to do with any new Proxmark is to update the firmware on it. The client is particularly choosy about being from the same version as the firmware, and generally updating firmware is a good thing to do.
Stock firmware First, clone the git repository at https://github.com/proxmark/proxmark3. As we’ll come on to, this isn’t actually the firmware which I’m running, but it’s a great place to start.
Compiling the firmware is easy; a simple make all is all it takes, as long as you have all of the dependencies (which are listed in the “COMPILING.
RFID is everywhere. In our contactless payment systems, in transport cards like Oyster and Chipkart and M-card season tickets, in hotel room doors, in office door locks, in some domestic door locks, in phones, even in some advertising posters. I’ve seen bluetooth devices use it to make pairing easier.
But how does it actually work? And how secure is it?
A few months back, I became fascinated by RFID, and decided to learn more about it.