Update path_notes.md

This commit is contained in:
Iceman 2019-09-04 11:01:49 +02:00 committed by GitHub
parent 0e3d1d4807
commit 4623340374
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -7,16 +7,50 @@ We are adapting the client to use searchFile when creating or calling a Proxmark
Here is where it tries to find the file and in which precedense order it takes.
## binary paths
This is where the executable / shellscripts will be copied to.
#
```
/usr/share/proxmark3
/usr/local/share/proxmark3
```
## binary paths
This is where the Proxmark3 executable / shellscripts will be copied to.
```
/usr/share/proxmark3/bin
/usr/local/share/proxmark3/bin
```
This is where the tools executable / scripts will be copied to
```
/usr/share/proxmark3/tools
/usr/local/share/proxmark3/tools
```
executables: mfkey32, mfkey32v2, mfkey64, nonce2key,
scripts: pm3_eml2lower.sh, pm3_eml2upper.sh, pm3_mfdread.py, pm3_mfd2eml.py, pm3_eml2mfd.py, findbits.py, rfidtest.pl, xorcheck.py
## JTAG stuff
This is where JTAG configurations will be copied to
```
/usr/share/proxmark3/jtag_openocd
/usr/local/share/proxmark3/tools/jtag_openocd
```
# Traces
Proxmark3 client has a lot of sample trace files for many different low frequency tags. They will be copied to
```
/usr/share/proxmark3/traces
/usr/local/share/proxmark3/traces
```
# Firmware paths
This is where the recovery / firmware files will be copied to.
bootrom.elf, fullimage.elf, proxmark3_recovery.bin (used for JTAG), sim011.bin, sim011.sha512.txt
```
/usr/share/proxmark3/firmware
/usr/local/share/proxmark3/firmware
```
## User given paths
```
~/.proxmark3/
@ -42,7 +76,7 @@ First instance where a file is found will be used in the client.
## What is where?
/resources
command like
The needed files for commands like hardnested, fido, EMV, iClass.
/dictionaries
Here you find the default dictionaries or your own used for commands like `hf mf chk`, `hf mf fchk`, `lf t55xx chk`