Skip to content
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

macOS Sequoia Access Local Network prompt #1841

Open
directionless opened this issue Aug 19, 2024 · 1 comment
Open

macOS Sequoia Access Local Network prompt #1841

directionless opened this issue Aug 19, 2024 · 1 comment
Assignees

Comments

@directionless
Copy link
Contributor

We're hearing reports that the new macOS Sequoia beta is causing prompts about Allow osquery to find devices on local networks This would be a horrific customer experience, and we need to understand more about what's happening...

  1. AFAIK this should only apply to things running in user context and accessing the network
  2. We run osquery in launchd context
  3. Except for screenlock, is that's what's happening?
  4. We run launcher in usercontext for the menu
  5. An Apple friend tells me there's an occasional bug where this triggers for launchd contexts

Threads:

@RebeccaMahany RebeccaMahany self-assigned this Aug 19, 2024
@RebeccaMahany
Copy link
Contributor

Reproducing the popup

Upgrade to Sequoia Beta. You will get the popup after upgrade.

To trigger the popup again, uninstall launcher, reboot the machine, and reinstall launcher.

In Privacy & Security => Local Network, you can see osquery is allowed or disallowed depending on how you responded to the prompt.

Actions that do NOT reproduce the popup

  1. Unloading and reloading launcher
  2. Refreshing all checks
  3. Querying the screenlock and curl tables via launcher interactive
  4. Uninstalling and reinstalling launcher without a reboot in between
  5. tccutil reset All io.osquery.agent (even with a reboot)

I have not yet found an actual consequence for selecting "Don't Allow". No error logs (osquery, launcher, or in the Console), and no missing data when running checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants