Thanks for the answer.
But for security reasons, my current architecture must be just one process for everything (capture, networking, etc). So right now my launch daemon just listening incoming connections, and after that just run a new process which do actual capture, networking and so on. The new process launches as current context - pre login or current console user, it depends on the current state.
Everything is working fine for older MacOS versions, but not for MacOS Sequoia. If I run a new process just using NSTask for example, everything is working except screen capture, so I assume that in the new MacOS version Apple wants to all capture process will start in different way.
I tried using NSWorkspace openApplicationAtURL, and sometimes it works on pre login context, but sometimes not.
So there is no other way to launch capture process except running it as launch agent? I can have several capture processes because for security reasons I need to have one connection - one process for that, and It should be completely isolated from different connection.
Topic:
Privacy & Security
SubTopic:
General
Tags: