Skype For Mac Os Sierra 10.12.5
Patch Description, Update for Skype For Mac (8.24.0.2). Bulletin Title, Skype Updates For Mac. Mac OS X - Sierra, Mac OS X - Sierra 10.12.5.
What model computers are you guys trying on? So far I've tried a 15' late 2013, 13' late 16 non touchbar, and a 13' late 16 touchbar all updated to 10.12.5 and was able to sucessfully connect 802.1X Available for: macOS Sierra 10.12.4 Impact: A malicious network with 802.1X authentication may be able to capture user network credentials Description: A certificate validation issue existed in EAP-TLS when a certificate changed. This issue was addressed through improved certificate validation. CVE-2017-6988: Tim Cappalli of Aruba, a Hewlett Packard Enterprise company I did get a 'Verify Certificate' before continuing to connect to my internal network here. Once I confirmed, I was on our internal network without any issues. How is your wifi authentication configured? Ours requires a root + intermediate cert to request a machine cert, then uses the machine cert to authenticate to wifi.
We deploy root + intermediate certs, AD cert request, and wifi config all through a configuration profile. On one machine, I was prompted for my login password to allow a change to the keychain. On another test machine, my machine was kicked off the wifi. In the keychain, I found the com.apple.network.eap.user.identity.wlan.ssid.WIFINAMEHERE had a red X and that the preferred certificate was set to None.
After I got back on the network, I restarted the computer and found that reconnecting to the network is all wonky now. WiFi won't even try to connect until after completely logged in and at the desktop (which means any Login triggers won't happen), Ethernet gets stuck in an infinite loop and never connects on its own. It gets a self assigned IP for a few seconds then falls back to 'not connected' and then gets a self assigned IP. Wash, rinse, repeat.
Download imessage for mac os x. The only way I can connect via Ethernet now is to click on Disconnect, wait a few seconds then click Connect. Then I get a valid IP. Same problem for us. Just submitted an enterprise case (71).
Only workaround that works for us is to manually go into the system keychain and set issuing and wireless certs to 'always trust' (the root is already set to always trust). Doesn't seem to be a good way to script this since the certs are deployed via config profile and already in the system keychain (so we can't really leverage a security add-trusted-cert command) Anyone having any luck setting the update to be ignored? I can't get sudo softwareupdate --ignore 'macOS Sierra Update-10.12.5' to actually ignore the update. I've also tried 'macOSSierraUpdate-10.12.5' 'Mac OS Sierra Update (10.12.5)' '10.12.5' and 'macOS Sierra Update' to no avail. We have update scheduled to push to clients this weekend but looks like I'm going to have to reschedule until this is fixed cause this is BAD. We recently moved away from using a SUS to instead lean on caching server since Apple is sunsetting their SUS - this also makes it easier for users not on site to keep up to date.
We've got a blacklist script that we run to ignore problematic updates, but unfortunately I can't find a phrasing for this update to successfully ignore it. This is the direction Apple has been moving in, so we were trying to skate to where the puck was heading, but unfortunately between the directory auth lockout issue in 10.12.2 and earlier, and now this - it's clear that we need to rethink that since Apple is failing to consistently test critical enterprise level functionality. To second, I had to sudo the ignore command to get the update to be ignored (wouldn't need to do so from a JAMF script).