search

Gator96100 / ProxSpace

Proxmark III develoment environment for Windows
269 stars 70 forks source link

mingw32: key "5F92EFC1A47D45A1" is unknown? #10

Closed feifeilanniao closed 5 years ago

feifeilanniao commented 5 years ago

image When i run the runme64.bat, some errors occur, what should i do to deal with these problem?

Gator96100 commented 5 years ago

Those errors are to be expected when ProxSpace is run for the first time. Are these errors appear after the first run? Please make sure you did not download ProxSpace via git.

feifeilanniao commented 5 years ago

Errors appear appear after the fisrt run. I download ProxSpace via chrome. image

Gator96100 commented 5 years ago

Run pacman --force -Syuu and try again.

feifeilanniao commented 5 years ago

image

Gator96100 commented 5 years ago

Try pacman --force -Syuu

feifeilanniao commented 5 years ago

Any different? image

Gator96100 commented 5 years ago

Github seems to have an inconsistency problem and I thought I forget the --force option. Due to the current Github problem this error could be caused by a corrupted download, try redownloading ProxSpace. Be sure to run ProxSpace as admin and that your firewall is not blocking connections. What Windows version are you running?

feifeilanniao commented 5 years ago

Windows 10. When i try to run runme64.bat as admin, it can't find the path.

Gator96100 commented 5 years ago

This looks like a DNS/Networking problem. Be sure there is no firewall that is blocking ProxSpace. You can try using a different DNS server, like the google DNS server (8.8.8.8).

Gator96100 commented 5 years ago

Any updates on this topic?

arslanbisharat commented 4 years ago

error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely error: mingw64: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown

Gator96100 commented 4 years ago

Make sure you are using the latest ProxSpace version. All ProxSpace version prior to v3.5 will no longer work as there was a keyring changes. See #41 #39