-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LuLu on macOS 15 RC: Connection attempts now attributed to the Terminal app instead of individual commands #634
Comments
I can confirm that there is something different now. With the update to macOS 15, The |
I am trying to figure out why my connections are dropping on 15.0. I am using wireguard and Lulu. I am connecting to my server using ssh, vnc and rd client. They are all dropping with a corrupted error. Even my Remote Desktop to windows connection is dropping. Also my vs code connection keeps dropping (it also uses ssh internally I believe). I can't test it without wireguard since my servers are all on it. |
This has now been confirmed, to yes, be due to an Apple bug in macOS 15, that is widely impacting many 3rd-party security tools, that then in turn causes macOS networking to break and/or having the "wrong" process associated with the network event. This has been reported to Apple (and was so before macOS 15 was released), who have confirmed the issue and are hopefully working on a fix. More info: "Apple’s new macOS Sequoia update is breaking some cybersecurity tools" |
Previously, on macOS 14.x or earlier, if you used a command like curl in the Terminal, LuLu would prompt with a message such as "curl wants to connect...".
However, on macOS 15 RC, LuLu now attributes the connection attempt to the Terminal app (or whichever app is running the command), displaying a message like "iTerm wants to connect..." instead of referencing the specific command (in this case, curl)
Note, some commands, like
/usr/bin/nscurl
, are unaffected. LuLu still prompts with "nscurl wants to connect..." on macOS 15.It seems something has changed in macOS 15, but I haven't found any mention of this in the macOS 15 RC release notes.
The text was updated successfully, but these errors were encountered: