mirror of
https://github.com/RfidResearchGroup/proxmark3.git
synced 2025-01-02 21:54:10 +08:00
Create extensions_notes.md
This commit is contained in:
parent
955eb2e536
commit
9fd646f25f
1 changed files with 16 additions and 0 deletions
16
doc/extensions_notes.md
Normal file
16
doc/extensions_notes.md
Normal file
|
@ -0,0 +1,16 @@
|
|||
# Notes on file extensions
|
||||
|
||||
The Proxmark3 client uses a wide range of files. Here is a brief recap to get you up to speed.
|
||||
|
||||
|
||||
- .exe windows executable
|
||||
- .bin binary file, can be firmware or memory dump of a tag
|
||||
- .eml text file, with memory dump of a tag
|
||||
- .mfd binary file, usually created with Mifare Classic Tool app (MCT), contains memory dump of tag. Very similar to .bin file
|
||||
- .json JSON file, usually settings file or it can also be a memory dump of a tag
|
||||
- .dic dictionary file. textual, with keys/passwords one line / key
|
||||
- .elf binary proxmark3 device firmware file.
|
||||
- .cmd text file, contains proxmark3 client commands used to call client with -s
|
||||
- .lua text file, contains lua script to be run inside client. or called with -l
|
||||
- .pm3 text file, with numbers ranging 0-255 or -127 - 128. Contains trace signal data for low frequency tags (data load)
|
||||
- .trace binary file, contains trace log data usually from high frequency tags. (hw trace load)
|
Loading…
Reference in a new issue