Auto load "mf_user_keys.dic" from spiffs [idea]

[ghiki]

Is your feature request related to a problem? Please describe.

When you do some attack, to load the keys file (whe you know, for testing for example) is very repetitive to do "-d xxx.dic" or "mem load -f xxxx" before doing

Describe the solution you'd like

Dictionary file (or files) in spiffs that loads when starting any type of attack (obviously, this will do only when "ifdef WITH_FLASH")

Describe alternatives you've considered

Load manually before with

mem load -f mfc_default_keys -m         -> upload MFC keys
mem load -f t55xx_default_pwds -t       -> upload T55XX passwords
mem load -f iclass_default_keys -i      -> upload iCLASS keys

or passing to the attack command manually

Additional context

[iceman1001]

you only need to upload the default dictionaries once on a RDV4 / spifffs based device. Its stored in eeprom and read from eeprom when called in a function that takes advantage of that functionality.

[ghiki]

Yep, but for example, a "hf mf autopwn" or any other, doesn't use any dic file although this file exists in the spiffs (only uses the hardcoded ones), the main idea is to use if the device has flash memory and a file with user Keys exist on It (now, if you want to use It, you need to load previously with "mem/data" command)

[iceman1001]

In that case are you thinking about updating hf mf autopwn to take advantage of the stored dictionary.

Uploading before to spiffs shouldn't affect autopwn to use it. Like I said you only need to upload once. Well, if the default dictionary file gets some additions you will of course re-upload it. Doesn't happen that often.

[jgoggan]

I really like this idea and thought the same thing the first time I started working with the PM3 hardware. On the previous hardware that I used, it automatically saved any previously cracked information so that if you ran a crack again on the same card, it would immediately complete because it already had the key handy. For the PM3, it always seemed funny to me that if I ran "hf mf autopwn" and it took a while and then cracked it -- and then I immediately ran "hf mf autopwn" again, it would do the entire crack again. I would love it if every time it was successfully at cracking a key, it stored it to a local mf_user_keys.dic that was auto-loaded for any new crack attempt. I mean, once it has the key, use it next time! :)

[iceman1001]

running attacks means running attacks, if you store found keys which autopwn does, you don't need to re-run attacks. You would use the already saved key file.