LuLu
LuLu copied to clipboard
LuLu silently prevents Homebrew downloads
I've noticed that despite manually adding a custom rule (allow for /usr/local/bin/brew
) for Homebrew’s brew executable, downloads triggered by Homebrew when installing or upgrading a dependency installed with it are blocked (silently) by LuLu and downloads can only proceed when LuLu is manually disabled.
I'm curious if anyone's found a way around this issue. I'm guessing it's caused by whichever process inside Homebrew actually deals with network connections not being adequately detected by LuLu.
Reproduction
- install Homebrew
- run
brew install ffmpeg
to for example attempt to download and installffmpeg
- notice multiple failures to download reported by Homebrew
- disable LuLu
- run
brew install ffmpeg
again - download and installation completes successfully
Could not reproduce:
$ brew install ffmpeg
==> Downloading https://homebrew.bintray.com/bottles/ffmpeg-4.0.2.high_sierra.bottle.tar.gz
==> Downloading from https://akamai.bintray.com/55/5522a58020c3b5c68e5628818ee746822fe38747810c29b4a
######################################################################## 100.0%
==> Pouring ffmpeg-4.0.2.high_sierra.bottle.tar.gz
🍺 /usr/local/Cellar/ffmpeg/4.0.2: 246 files, 49.7MB
brew
started connections using one curl
and two git-remote-http
processes, make sure you don't have them blocked for some reason.
I ran "brew update" and it just kept on hanging in an unresponsive manner. I disabled LuLu and the command finished without issue.
I use homebrew all the time with no issue, there must be some rule in there that is blocking it. Maybe try a fresh install of LuLu
I'm having this same now.
Lulu: v. 1.1.2
Homebrew: 2.1.6
Homebrew/homebrew-core: (git revision b639; last commit 2019-07-02)
I'll try reinstall later, but due to this, I'll lost all my rules? 🤔
Any findings on that? Facing the same issue in 2023 :D
Can you run:
log stream --level debug --predicate="subsystem='com.objective-see.lulu'"
from the Terminal and then run some brew commands (that are failing).
The log should show what/why they are being blocked. Please post any findings here, or email: [email protected]
Mahalo!
Might help someone in the future: I had the same issue, and I discovered (using log stream command) that curl was blocked.