Hacker News Reader

Comment by habinero | Hacker News Reader

That's...what background processes do? They're supposed to run occasionally and be resilient to disruption.

But if you wanna be afraid of boring ordinary things, you go right ahead.

Even excusing that daemon, here is a list of processes which have attempted to contact Apple in the past 24 hours, according to Little Snitch. I am certain this is not even a complete list, because macOS is closed source and likely can bypass application firewalls altogether:

    akd -> gsa.apple.com
    nsurlsessiond -> gateway.icloud.com
    nsurlsessiond -> mesu.apple.com
    nsurlsessiond -> gdmf-ados.apple.com
    nsurlsessiond -> gdmf.apple.com
    adprivacyd -> bag.itunes.apple.com
    CloudTelemetryService -> gateway.icloud.com
    cloudd -> gateway.icloud.com
    amsondevicestoraged -> bag.itunes.apple.com
    tipsd -> ipcdn.apple.com
    parsec-fbf -> fbs.smoot.apple.com
    parsec-fbf -> swallow.apple.com
    com.apple.geod -> gspe1-ssl.ls.apple.com
    identityservicesd -> init.ess.apple.com

Again, I have never used iCloud/Apple services, turned off all available telemetry options and did not open any Apple applications while all this took place (I only use Firefox and iTerm). Almost all of these processes lack a man page, or if they have one, it's one-line nonsense which explains nothing. This is beyond unprofessional.

Reply on news.ycombinator.com