hi to all! today i tryed e dump hf autopwn end it generated only 2 files: dump.bin and key.bin
is it changed anything in rrg 20260802 for prox easy? thank you
@Aoxhwjfoavdlhsvfpzha @Pilgrimsmaster @Equipter
Since there are so many different branches and versions of firmware, the very first question you need to answer is which version are you running? Show us the startup screen that details the version of firmware and client you have
4 Likes
Ok so you’re basically up to date with Iceman branch. I believe json files are still supported but not output by default? Check the available command parameters.
@Iceman is json still supported or was it completely removed?
2 Likes
huh according to the git commit log, EML file export was removed in October 2023 but JSON should still be working. however, key dumps specifically never output in JSON format, only BIN. but, you should have at least a dump file in JSON format.
can you confirm the actual command you ran to do the autopwn? a screenshot of the command and initial output would be ideal.
ooo hmm… actually looks like a bug introduced in this commit;
issue filed;
So, you can roll back to a version prior to the commit date to get JSON output, or wait for the fix and update.
2 Likes
thank you @amal exactly i was tryng a dump of a static encrypted nonce, i was sure of that propriety but with this new firmware i don’t see the encrypted type and i see the autopwn go ahed!!! i was very happy of that but at least i noticed the .json absence. i don’t need it early so i can wait sure of the result, very happy to haven’t sniff anything!
1 Like
.json format is the one we gonna use in the future. .bin will be parsed out slowly , .eml should already be gone.
You found the bug with your good GH issue.
3 Likes
i’m ordering some FM11RF08S to test with before pushing a PR
4 Likes
I pushed the fix already and some more.
Should be more consistent in the behavior for “autopwn” now.
It is starting to be quite a complex command with all different implementations of attacks.
Which doesn’t mean everyone who develops can follow the internal logic. I am struggling with it too.
5 Likes
Apologies for my ignorance, but I keep seeing the same version on proxmarkbuilds.org (02/08/2026); how can I try out the fix? Thanks, and sorry.
@amal
Its probably up to date on github
Do you need instructions?
cd proxmark3
git pull
make clean && make -j4
./pm3-flash-all
./pm3
2 Likes
yeah, this is a place where people take releases from github and build them into binaries.. as such 1) releases are not happening for every code update, only periodically, and 2) then someone has to care enough to build binaries of the latest release.. so you’re hitting two time delays there. Even though the update has been merged into the current repo codebase, a release with that update has not been published yet, and once it is, you will have to wait until someone takes that release and makes a new build with it and publishes that to proxmarkbuilds.org.
your better bet is to learn how to pull down the red hot current code directly from the github repo and compile it yourself… the instructions Pilgrims posted above is what you’d do if you’ve already done this.. however since you’re using proxmarkbuilds then you likely don’t have any actual code to “git pull” to update to the latest or compile once updated.. you have a pre-built binary compiled by someone else and published to proxmarkbuilds. if you want to get gud and L33T then nuke your current proxmark setup and check this guide to set up proxspace .. this is a pseudo-linux environment for windows just to run all the *nix stuff you need to get current code from github (using git clone to get the code, then git pull to update later), compile it into the client and firmware, and flash the firmware you just made to your proxmark hardware.
3 Likes
