Struan Clark a23a54d9ad fix: combine F52100 AIDs

2026-02-02 14:25:32 -07:00

..

hardnested_tables

Bring LZ4 support for hardnested tables

2023-07-15 22:58:00 +02:00

aid_desfire.json

fix: combine F52100 AIDs

2026-02-02 14:25:32 -07:00

aidlist.json

AID list: added Crescendo AIDs

2025-08-17 16:28:23 +02:00

capk.txt

move capk.txt to resources/

2019-08-30 02:10:55 +02:00

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

move defparams.json to resources/emv_defparams.json

2019-08-30 02:18:14 +02:00

hardnested_bf_bench_data.bin

move bf_bench_data.bin to resources/hardnested_*

2019-08-30 08:53:24 +02:00

hf_fido2_defparams.json

Rename hf-fido2_defparams.json to hf_fido2_defparams.json

2021-06-15 13:46:27 +03:00

iceman.txt

fix flashing long line

2025-09-21 17:38:37 +03:00

iclass_decryptionkey.bin

Add iCLASS key

2021-10-16 21:06:58 +02:00

iclass_dump.bin

move iclass_dump.bin in resources/

2019-08-30 01:23:10 +02:00

key_retail.bin

hf 14a info - add MFC EV1 signature checks

2021-02-19 13:39:35 +01:00

mad.json

addition

2025-07-28 15:44:10 +02:00

oids.json

move oid.json to resources/

2019-08-30 02:00:41 +02:00

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

smart commands - most use cliparser, moved sim fw file to RESOURCES

2021-01-07 12:31:29 +01:00

sim011.sha512.txt

smart commands - most use cliparser, moved sim fw file to RESOURCES

2021-01-07 12:31:29 +01:00

sim013.bin

add updated sim module firmware v4.13, this is breaking change for smart category commands

2022-12-09 07:36:02 +01:00

sim013.sha512.txt

add updated sim module firmware v4.13, this is breaking change for smart category commands

2022-12-09 07:36:02 +01:00

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

added a sample VAS private key to client/resources folder. Updated helptexts

2023-07-09 13:00:09 +02:00