Windows 11 vs Windows 10 Laptop vs Mac OS 14 Laptop for Proxmark3

I’ve been trying to crack a Mifare Classic 1K fob with the Flipper Zero but hit the wall after trying everything suggested by the community here at DT (another thread). I’m still a newb so I am going to try to lay out my question and the thought process behind it.

I decided to step up my game and invest and get either a Proxmark3 Easy or RDV4 I don’t mind spending more money for the RDV4 (I can hear the adage “buy cheap buy twice” ringing in my ear) but I am now realizing that since I am Mac based I will also need to buy a Laptop (now the investment is really snowballing) running Windows to even operate the PM3. So my question is should I get a Windows 10 or Windows 11 laptop? (have seen some discussions about Windows 11 being glitchy ((if you recommend Windows 11 – does it matter if it is Home or Pro?)))

Unless someone chimes in and says dude its so easy to run this on Mac OS 14+ which of the below combos do you all recommend for a newb to get the job done cracking this darn Mifare Classic 1K fob (pictured below):

PM3 RDV4 + Windows 10 Laptop = 380 + ~185 = 565

Dell Laptop running Windows 10

PM3 Easy + Windows 10 Laptop = 89 + ~185 = 274

I do want to be able to write the cracked card info to a card that I can use as a backup to the fob I have-- so can both the Easy and RDV4 do that function the effectively?

Thanks again in advance and if anyone has any recommendations on a cheap windows laption on Amazon that is good enough to get the job done that would be greatly appreciated.




Thanks!

Get an Easy, preferably from DT

Mac OS is supported, at a minimum get a PM3 and try it on Mac before purchasing an entire new laptop for it, worst case is you have to wait a little longer

Also, do you have an android phone? If you do, and you haven’t already tried Mifare Classic Tool (MCT), that could be worth a try too

5 Likes

Awesome thanks for the quick response–much appreciated!

I used to have an Android phone–maybe I’ll see if I can pickup a used one for cheap to try MCT–thanks for the idea!

3 Likes

I use a PM3 on my Mac and didn’t have any issues now that my environment is setup properly.

If you do have issues I have no problem helping you step through then to get you up and running also

5 Likes

Awesome! @Hamspiced Just ordered the PM3 Easy from DT. Thanks for letting me know it’s possible—will definitely reach out if I get stuck. Thanks again!

3 Likes

Do you have an m1 Mac?

1 Like

@Hamspiced I think I just missed the M1 – I have the following:

MacBook Pro - 13 inch 2020
Processor - 1.4 GHz Quad-Core Intel Core i5
Mac OS Sonoma 14.5

Let me know if this is a deal breaker (it could be time for me to upgrade anyway) and if you have some resources for me to start preparing the environment–I checked if I had homebrew installed as I remember doing a Ruby on Rails application tutorial during Covid. I entered: brew help and got the below back (so I think I have it installed already):

% brew help
Example usage:
brew search TEXT|/REGEX/
brew info [FORMULA|CASK…]
brew install FORMULA|CASK…
brew update
brew upgrade [FORMULA|CASK…]
brew uninstall FORMULA|CASK…
brew list [FORMULA|CASK…]

Troubleshooting:
brew config
brew doctor
brew install --verbose --debug FORMULA|CASK

Contributing:
brew create URL [–no-fetch]
brew edit [FORMULA|CASK…]

Further help:
brew commands
brew help [COMMAND]
man brew
https://docs.brew.sh

Then I entered brew -v into my terminal and got the below:

Homebrew >=2.5.0 (shallow or no git repository)

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

Homebrew/homebrew-core (no Git repository)

1 Like

No no no, you’re good! M1 macs seem to have more “problems” getting the environment setup.

For you, since you already have Homebrew installed the setup should be simple simple.

There are two ways to do it. one Via brew and two via github. Brew may be the easier option for you. Be warned i never had a PM3 when i had my Intel mac so i never was able to get brew functioning to use it but i can walk through the steps with brew with you.

  1. Open up terminal or Iterm and run
    Brew Update
    and then
    Brew Upgrade
  2. Grab a coffee, eat some lucky charms and let it churn
  3. After its finished install Xquartz by running
    brew install xquartz
  4. tap the Iceman Repo by running
    brew tap RfidResearchGroup/proxmark3
  5. Next install Proxmark3
    brew install --with-generic proxmark3

edit: you may get yelled at by brew for this because there is the official outdated proxmark repo. if so run

 brew install --HEAD --with-generic rfidresearchgroup/proxmark3/proxmark3

From here you should (SHOULD) be all set. @amal flashes these beforehand so all you need to do is plug it in to your mac and run pm3 and you should be good. HOWEVER… OSX loves to call me a liar (sassy little bitch it is, i swear…) so youll probably run into a snag, issue, or problems with the port. if that happens dont worry… its all part of the plan (repeat endlessly).

2 Likes

If you’re feeling adventurous, you could also use the scripts over at:
https://siliconbased.us/pm3/install/

To automate some of the install for you (Shameless plug :slight_smile: )

2 Likes

well deserved plug.

Another great Aox tool :+1:

3 Likes

@Hamspiced @Aoxhwjfoavdlhsvfpzha I had an old version of Homebrew and did the brew update and brew upgrade (I think one of these didn’t work and I downloaded the Homebrew-4.4.5.pkg file and upgraded that way) and then ran brew cleanup but when I run “brew doctor” here is what I get now:

% brew doctor

Please note that these warnings are just used to help the Homebrew maintainers

with debugging if you file an issue. If everything you use Homebrew for is

working fine: please don’t worry or file an issue; just ignore this. Thanks!

Warning: No Cask quarantine support available: unknown reason.

Warning: Some installed formulae are deprecated or disabled.

You should find replacements for the following formulae:

openssl@1.1

Warning: Unbrewed dylibs were found in /usr/local/lib.

If you didn’t put them there on purpose they could cause problems when

building Homebrew formulae and may need to be deleted.

Unexpected dylibs:

/usr/local/lib/libavcodec.55.52.102.dylib

/usr/local/lib/libavformat.55.33.100.dylib

/usr/local/lib/libavutil.52.66.100.dylib

/usr/local/lib/libswscale.2.5.102.dylib

/usr/local/lib/libx264.129.dylib

Warning: You have unlinked kegs in your Cellar.

Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on

those kegs to fail to run properly once built. Run brew link on these:

openssl@3

Do I try to fix all this or would you suggest that I do an uninstall and do a fresh install to start over with a clean homebrew without all the fixes?

Thanks again for your help!

2 Likes

run brew link openssl@3

Then you can run brew doctor again and see if the same warning pops up

Honestly updating and upgrading brew like i posted above should fix these issues

3 Likes

It’s easy to run this on Linux, and Mac OS shouldn’t be far behind as it’s also a Unix flavored OS.

Also, this is great advice:

3 Likes

With all the help I received on this forum (Aox rocks!) I wouldn’t have any concerns recommending the use of a PM3 on Mac. Mine is also a DT Easy. Worked for me.

4 Likes

@Hamspiced Thanks! I ran brew link openssl@3 and then brew update and then brew upgrade and then brew doctor one more time and it cam back with this:

% brew doctor

Please note that these warnings are just used to help the Homebrew maintainers

with debugging if you file an issue. If everything you use Homebrew for is

working fine: please don’t worry or file an issue; just ignore this. Thanks!

Warning: No Cask quarantine support available: unknown reason.

Warning: Some installed formulae are deprecated or disabled.

You should find replacements for the following formulae:

openssl@1.1

Warning: Unbrewed dylibs were found in /usr/local/lib.

If you didn’t put them there on purpose they could cause problems when

building Homebrew formulae and may need to be deleted.

Unexpected dylibs:

/usr/local/lib/libavcodec.55.52.102.dylib

/usr/local/lib/libavformat.55.33.100.dylib

/usr/local/lib/libavutil.52.66.100.dylib

/usr/local/lib/libswscale.2.5.102.dylib

/usr/local/lib/libx264.129.dylib

Since I am not getting the “Your system is ready to brew” back do I just continue on or keep trying to fix these annoying errors?

Thanks again!

1 Like

its worth removing those files. Openssl@1.1 and th elisted dylibs. that way the errors will go away

2 Likes

@Hamspiced is that prompt i need to run to fix it: “Openssl@1.1 and th elisted dylibs”

Sorry I am lost when it comes to this

1 Like
brew uninstall --force Openssl@1.1

And then type the following to remove those 5 files.

rm /usr/local/lib/libavcodec.55.52.102.dylib

rm /usr/local/lib/libavformat.55.33.100.dylib

rm /usr/local/lib/libavutil.52.66.100.dylib

rm /usr/local/lib/libswscale.2.5.102.dylib

rm /usr/local/lib/libx264.129.dylib

2 Likes

@Hamspiced Ok great I did that and then ran brew update and brew upgrade I am now down to just one warning after entering brew doctor:

% brew doctor

Please note that these warnings are just used to help the Homebrew maintainers

with debugging if you file an issue. If everything you use Homebrew for is

working fine: please don’t worry or file an issue; just ignore this. Thanks!

Warning: No Cask quarantine support available: unknown reason.

Let me know if you can help me with that last one?

Thanks again!

1 Like

you can proceed, that isnt a problem at all.

2 Likes