Proxmark 3 Easy Error

Hi,
I’m new to proxmark. Forgive me if I am posting in the incorrect forum. Hoping someone can point me in the right direction. I am receiving the following error when I execute the “runme64.bat” file:
error: mingw-w64-x86_64-bzip2: signature from “David Macek david.macek.0@gmail.com” is unknown trust
:: File /var/cache/pacman/pkg/mingw-w64-x86_64-bzip2-1.0.8-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).

error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

Has anyone encountered this?

You could try one of the pre-compiled windows binaries from this site:

https://proxmarkbuilds.org/

you want the recommended
Latest RRG / Iceman generic build for Proxmark3 devices (non RDV4), for Proxmark3 Easy, RDV1, RDV2, RDV3, etc etc
option

or, just click this download link:
https://proxmarkbuilds.org/latest/rrg_other

2 Likes

As for your original error, unfortunately I was unable to replicate it

This site:

https://wiki.archlinux.org/title/Pacman/Package_signing
says:

Pacman does not seem to always be able to check if the key was received and marked as trusted before continuing.

So maybe retry the installation and see if the error occurs again

1 Like

Generally speaking it’s probably best to wipe and reattempt your proxspace deployment. On Windows I’ve had better success putting proxspace in a folder just off the C:/ that isn’t too long or contains spaces. I typically go for C:/proxspace

The first time you run the bat file after downloading it will set up the environment. If there are path or permissions issues on your proxspace folder it will have a hard time.

Also I’ve seen similar issues with running proxspace the first time but these were related to a bad release and things got cleared up a couple days later. Wipe and redownload was the solution once the release was sorted and bumped on GitHub.

2 Likes

Thank you. The precompiled binaries worked like a charm.

2 Likes