Homebrew SECURITY FLAW! You could EASILY be ATTACKED! 

Another approach is to create a new 'brew' user on the mac, and use it to install everything. You change to that user to add new binaries, but never use the 'brew' user account for anything else. Not requiring a password to add software, or to alter the files is /usr/local, is a huge security hole.

This is why I prefer macports over Homebrew.

I didn't quite catch what you did there to secure it.

thank you in advance for your time! : )

How about creating a script that goes back to a secure bin folder after downloading and installing any formulas and or casks?

Hi Apple Ninja, great video! -- thank you. Q: I’m a bit confused though could you please clarify. As I understand your solution to this brew flaw is to chown the permissions back and forth. In other words you maintain permissions as: sudo chown root:wheel /usr/local/bin and then sudo chown macguy:admin /usr/local/bin when you want to install a formula? Is that correct? And what about: /usr/local/opt Q: Would your permissions toggling be advisable there, too? And if not why not?

What about the original location where the alias is pointing to? You can still overwrite that? How about the brew executable itself or it’s libraries?

what if nothing pops up on brew list does that mean theres nothing to worry about as far as security ?

Also, what about MacPorts, does it also have security flaws?

what should we use then?