Why is ThinOS trying to reach captive.apple.com?

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #105118
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    Looking through some log files from ThinOS 9.1.2101 and the log located in compat\linux\var\log\webapp there is com.thinos.sysmgr log file.  This makes no sense to me why ThinOS is trying to reach out to Apple over http?  We caught it first looking at network traces with security and someone mentioned the thin client trying to reach out to Apple but it was being blocked at the firewall.  I said that makes no sense but leave it blocked.  Then I found it in this log…

    2021-04-15T14:44:58.207Z:[INFO] wms: current build first boot: true, previous OS build is 9.1.1131

    2021-04-15T14:44:58.207Z:[INFO] wms: clean RegistrationData on first boot after upgrade from 9.1.1131

    2021-04-15T14:44:58.211Z:[INFO] [HTTPS:] HTTP request error => Error: getaddrinfo ENOTFOUND captive.apple.com captive.apple.com:80
    2021-04-15T14:44:58.994Z:[INFO] wms: info: failed to load Registration. undefined
    2021-04-15T14:44:59.006Z:[INFO] wms: connectivity available…
    2021-04-15T14:44:59.007Z:[INFO] wms: auto discovery timeout is expired…

    #105136
    Avatarsimond83
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    I bet you they’ve plugged in their phone to charge via the device off the USB. Then Apple is trying to call home.

    #105137
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    I would have thought the same but this is my thin client I have at home and I have no Apple device connected to it. Dell keyboard and mouse, Logitech C920 camera and a Plantronics headset is all that is connected.

    The device that was in-office where we did a network capture also had no Apple product connected to it. This is very odd.

    #105205
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    Ahhhhhh, it’s the captive portal WiFi self test so to speak.

    Apple uses captive.apple.com to detect that you are on a captive network, and once it detects this, it does some very Apple-specific actions. Google and Microsoft use the same method, except with a different url.

    If any application wants to detect it is on a captive network, it can connect to any of these websites (captive.apple.com or the Google or Microsft site), check the result, and that way detect a captive network. You absolutely don’t need to run on an Apple, Google or Microsoft device for this.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.