Lucas Manuel Rodriguez

Ah, I see, thanks for the detailed report. I'll share with the team.

In case you missed it: Don't forget the corresponding [osquery-perf](https://github.com/fleetdm/fleet/blob/main/cmd/osquery-perf/agent.go) changes.

I guess we shouldn't merge this until we implement the vulnerability check part?

OK, let's not merge yet (to reduce risk), but changes so far look great!

+1 to all the above. We should define a separate endpoint for Fleet Desktop only, for fetching the policies. Why? 1. What Tomas said above regarding API compatibility and not...

@roperzh This is ready to be re-tested by @xpkoala, right?

@roperzh I think that by testing the packages downloaded from a Fleet Sandbox is the proof this is working as expected. (No need for Reed to setup credentials.) What do...

Ah good point. It does make sense for someone other than you (@roperzh) to test this.

Wasn't able to reproduce on my end. Please check orbit logs: `/var/log/orbit/orbit.stderr.log`.

> W0708 11:46:23.758304 1800450048 watcher.cpp:397] osqueryd worker (33720) stopping: Memory limits exceeded: 262242304 Curious as to which query might be causing that... (Hopefully https://github.com/osquery/osquery/issues/7658 will help :)