XaviTorello / Mifare Classic Toolkit
Licence: gpl-3.0
RFID / NFC :: Mifare Classic 1k info and tools
Stars: ✭ 46
Projects that are alternatives of or similar to Mifare Classic Toolkit
Chameleonmini Rebootedgui
Windows based GUI for Chameleon Mini, the contactless smartcard emulator (NFC/RFID)
Stars: ✭ 159 (+245.65%)
Mutual labels: nfc, card
Chameleonmini
The ChameleonMini is a versatile contactless smartcard emulator compliant to NFC. The ChameleonMini was developed by https://kasper-oswald.de. The device is available at https://shop.kasper.it. For further information see the Getting Started Page https://rawgit.com/emsec/ChameleonMini/master/Doc/Doxygen/html/_page__getting_started.html or the Wiki tab above.
Stars: ✭ 1,133 (+2363.04%)
Mutual labels: nfc, card
Mfrc522 Rpi
🔑 Control your MFRC522 RFID Module with your Raspberry-pi and JavaScript
Stars: ✭ 91 (+97.83%)
Mutual labels: nfc, card
Chameleonmini Rebooted
Chameleon Mini revE rebooted - Iceman Fork, the ChameleonMini is a versatile contactless smartcard emulator (NFC/RFID)
Stars: ✭ 208 (+352.17%)
Mutual labels: nfc, card
Open Home Automation
Open Home Automation with Home Assistant, ESP8266/ESP32 and MQTT
Stars: ✭ 820 (+1682.61%)
Mutual labels: arduino, nfc
Hass Yaap
Yet another alarm (control) panel for Home Assistant.
Stars: ✭ 44 (-4.35%)
Mutual labels: arduino
Emv Nfc Paycard Enrollment
A Java library used to read and extract data from NFC EMV credit cards (Android/PCSC).
Stars: ✭ 1,009 (+2093.48%)
Mutual labels: nfc
Wattuino
Arduino compatible Boards and Modules based on Microchip ARM and AVR Microcontroller
Stars: ✭ 41 (-10.87%)
Mutual labels: arduino
Esp8266 arduino temperature nodes
Allows a NodeMCU module to be used to capture/display/serve temperature information - uses OLED display and DHT or Dallas type temp sensors
Stars: ✭ 44 (-4.35%)
Mutual labels: arduino
Fram mb85rc i2c
Arduino library for I2C FRAM - Fujitsu MB85RC & Cypress FM24, CY15B
Stars: ✭ 41 (-10.87%)
Mutual labels: arduino
Rf1101se Teensy
Driving one of those cheap RF1101SE boards with a Arduino or Teensy
Stars: ✭ 45 (-2.17%)
Mutual labels: arduino
Bangoskank
A sketch to use an ESP8266 to flood the surrounding area with SSIDs of your choosing.
Stars: ✭ 46 (+0%)
Mutual labels: arduino
Iltms automated dust collection
Fully automated dust collection system with blast gate control
Stars: ✭ 45 (-2.17%)
Mutual labels: arduino
Esp8266 Relay
Relay control from a web page using the ESP8266 chip
Stars: ✭ 42 (-8.7%)
Mutual labels: arduino
Scrollingcardview
A card view widget for iOS that will grow with its content, enabling scrolling when the content is larger than the view.
Stars: ✭ 42 (-8.7%)
Mutual labels: card
RFID-toolkit
Set of tools needed to interact with RFID tags over arduino
Basic info about Mifare Clasic 1k
Memory layout
Keys
Each sector of a MIFARE Classic card has two authentication keys: key A and key B. These two keys together with access conditions are stored in the last block of each sector (the so-called sector trailer). The sector trailer looks like this:
+-----------------------------+--------------+----+-----------------------------+
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 |
+-----------------------------+--------------+----+-----------------------------+
| Key A | Access Conditions | Key B |
| (6 bytes) | (4 bytes) | (6 bytes) |
+-----------------------------+--------------+----+-----------------------------+
The access conditions define how you can access the blocks in the sector:
the commands you can issue after authenticating with key A (read, write, value block operations),
the commands you can issue after authenticating with key B (read, write, value block operations),
if key B is used as an authentication key at all.
Typical scenarios are:
Authentication is only possible with key A. Key A has read-only access.
Authentication is only possible with key A. Key A has read/write access.
Authentication is possible with both keys. Key A has read-only access. Key B has read/write access.
Authentication is possible with both keys. Key A and B have read-only access.
You can find a full description of the possible access conditions in the MIFARE datasheet.
from http://stackoverflow.com/a/28051227
Default keys list
ffffffffffff
a0b0c0d0e0f0
a1b1c1d1e1f1
a0a1a2a3a4a5
b0b1b2b3b4b5
4d3a99c351dd
1a982c7e459a
000000000000
aabbccddeeff
d3f7d3f7d3f7
aabbccddeeff
714c5c886e97
587ee5f9350f
a0478cc39091
533cb6c723f6
8fd0a4f256e9
Game rules
* MIFARE Classic 1K (MF1S503x):
* Has 16 sectors * 4 blocks/sector * 16 bytes/block = 1024 bytes.
* The blocks are numbered 0-63.
* Block 3 in each sector is the Sector Trailer. See http://www.mouser.com/ds/2/302/MF1S503x-89574.pdf sections 8.6 and 8.7:
* Bytes 0-5: Key A
* Bytes 6-8: Access Bits
* Bytes 9: User data
* Bytes 10-15: Key B (or user data)
* Block 0 is read-only manufacturer data.
* To access a block, an authentication using a key from the block's sector must be performed first.
* Example: To read from block 10, first authenticate using a key from sector 3 (blocks 8-11).
* All keys are set to FFFFFFFFFFFFh at chip delivery.
* Warning: Please read section 8.7 "Memory Access". It includes this text: if the PICC detects a format violation the whole sector is irreversibly blocked.
* To use a block in "value block" mode (for Increment/Decrement operations) you need to change the sector trailer. Use PICC_SetAccessBits() to calculate the bit patterns.
, from https://github.com/miguelbalboa/rfid/blob/master/MFRC522.h
References
Note that the project description data, including the texts, logos, images, and/or trademarks,
for each open source project belongs to its rightful owner.
If you wish to add or remove any projects, please contact us at [email protected].