![]() ![]() ![]() Since port 7000 isn't listed as anĪirPlay port on Apple's list of ports used by Apple products, I blocked it. However, my AirPlayXPCHelper tried toĬonnect to something on port 7000. Furthermore, every individual XPC service is sandboxed so it can't affect other processes. Throw it in an XPC!" which sounds pretty awful but whatever, that's not This seems like Apple is saying "got buggy code? Don't fix it, just ![]() User-facing program won't, and can simply restart the XPC service. Likely to crash, throw it in an XPC so that even if it crashes, the main Apple recommends using XPCs forįault-tolerance: if you have some component in your application that is Is user-level service (like a daemon) that runs in the background and Here's what I've found on some of the processes you might have noticed if you ever disabled the protected rules:ĪirPlayXPCHelper - Background on XPCs: An XPC ![]() Running processes through dtruss, Wireshark, and other tracing tools,Īnd occasionally breaking my computer along the way. I've had someĪdventures selectively enabling and disabling services with launchctl, I decided I would actually bother to investigate what all thoseĭifferent system-owned processes and daemons did. When it could be hijacked just like any user process? (For example, see this mDNSResponder vulnerability from June of this year that allows for arbitrary code execution. The traffic that one little MacBook can send! I wasn't satisfied to justįilter my user-level programs - why should I trust a system process Recently picked up Little Snitch and I've had a fun time watching all Ever wonder what all those system processes are doing? So did I. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |