This website requires JavaScript.
Explore
Help
Sign In
dandri
/
proxmark3
Watch
1
Star
0
Fork
0
You've already forked proxmark3
mirror of
https://github.com/RfidResearchGroup/proxmark3.git
synced
2026-05-28 20:44:20 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
7bdd677e3687e1409628629ffd4e3ab8699358ec
proxmark3
/
client
/
resources
T
History
kormax
2fce3393ea
Add LEAF DESFire AID values to dictionary
2026-03-06 18:18:33 +02:00
..
hardnested_tables
Bring LZ4 support for hardnested tables
2023-07-15 22:58:00 +02:00
aid_desfire.json
Add LEAF DESFire AID values to dictionary
2026-03-06 18:18:33 +02:00
aidlist.json
AID list: added Crescendo AIDs
2025-08-17 16:28:23 +02:00
capk.txt
…
ecp_taxonomy.json
add new AID & ECP definitions
2024-05-21 22:49:06 +03:00
ecplist.json
Update ecplist.json
2025-11-01 12:23:58 +02:00
emv_defparams.json
…
hardnested_bf_bench_data.bin
…
hf_fido2_defparams.json
…
iceman.txt
fix flashing long line
2025-09-21 17:38:37 +03:00
iclass_decryptionkey.bin
…
iclass_dump.bin
…
key_retail.bin
…
mad.json
addition
2025-07-28 15:44:10 +02:00
oids.json
…
pm3_generic_private_key.pem
this commit refactors the signature checks. First we introduce a common pm3 generic private / public key pair in order to allow for users to self sign their own modded device. The verification checks now looks at both hard coded public keys. If a vendor wants to add their own public key thus allowing for a simple way for us to identify their devices they can now do so. The downside is that the firmware mismatch detection becomes a bit dodgy.
mem info; mem info -v; mem info -s -p <filename.pem>; mem info -s -p <filename.pem> -w
contains the changes. OBS! when
-w
be careful to not overwrite your genuine RDV4 signature. As always, with great power comes great responsibility
2025-09-25 19:44:36 +02:00
pm3_generic_private_key.sha512.txt
this commit refactors the signature checks. First we introduce a common pm3 generic private / public key pair in order to allow for users to self sign their own modded device. The verification checks now looks at both hard coded public keys. If a vendor wants to add their own public key thus allowing for a simple way for us to identify their devices they can now do so. The downside is that the firmware mismatch detection becomes a bit dodgy.
mem info; mem info -v; mem info -s -p <filename.pem>; mem info -s -p <filename.pem> -w
contains the changes. OBS! when
-w
be careful to not overwrite your genuine RDV4 signature. As always, with great power comes great responsibility
2025-09-25 19:44:36 +02:00
sim011.bin
…
sim011.sha512.txt
…
sim013.bin
…
sim013.sha512.txt
…
sim014.bin
fixed sim fw
2023-09-29 20:50:39 +02:00
sim014.sha512.txt
thanks @gentilkiwi for pointing it out
2023-09-29 21:41:27 +02:00
vas_privkey.der
…