Finally! We've figured out how to make Xammp Secure!

You'll be happy to know that if you root around on the Internet cutting and pasting random snippets of code into your terminal, eventually you'll realize that there was a typo in the main front page of the MacOS version of Xampp's security page.
Once you've filed a bug report on the matter-- or rather, hunted around on phpfriends.com's website looking for a place to file the bug, but then giving up because you really don't care so much-- go ahead and execute the "call."
That's what they mean, you know? When they say "call." They want you to type a command into the terminal. Fire up your little dictionary and see that "call" in computing means "to cause the execution of (a subroutine.)"
If only they gave you the proper call, you probably could have figured this out all by yourself.

See down at the bottom of the "Security" window in your xampp page? It says:
To fix or close all these matters simply call /Applications/xampp/xamppfiles/xampp security This will start an interactive program.

They mean "mampp."
Seriously.

The bottom of the page, on the MacOS version of Xampp, should say :
To fix or close all these matters simply call /Applications/xampp/xamppfiles/mampp security This will start an interactive program.

Go ahead and paste /Applications/xampp/xamppfiles/mampp security" into your terminal. Amazing. When you call the right file, the right file is called.

Now, let's get some Drupal on.