Fixed latest versions of proxmark3 not working. #70
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Recent releases of proxmark3 (iceman) don't work (at least on my proxmark? I don't know when that changed, but I'll explain)
The program is looking for the
os:string to get a version and basically even just try and connect to the device, but on recent proxmark3 firmware builds (or is it the software?), while runninghw version, instead of having a lineos: [...], you get a lineOS......... [...].(
OS......... Iceman/master/v4.20728-146-ge10e1135d-dirty-suspect 2025-11-12 19:07:28 7bbbe9cd7in my case).I fixed the issue by using a regular expression matching both the old
os:string and the newOS.........one, parsing the version properly, without compromising backwards compatibility.Thanks for reading all this! :D