Recent updates to this article:
| Date |
Update |
| May 22, 2018 |
Minor formatting changes. No content updates. |
| September 26, 2017 |
Updated McAfee Agent information to include new hotfix release. |
| August 30, 2017 |
Added McAfee Agent information. |
| August 25, 2017 |
Minor typographical change. |
| August 17, 2017 |
Added McAfee Client Proxy for Mac 2.3.1 as an affected product. |
The Apple developer certificate that is used for signing Mac installer packages expired on August 14, 2017. Hence, McAfee is posting updated Mac installer packages signed with a new Apple developer certificate.
Environments affected by this change:
| Environment |
Action to be taken |
| Mac products that are already installed (standalone and ePolicy Orchestrator [ePO] managed) |
No action is required. |
| New deployments from ePO on or after August 14, 2017 |
You must:
- Remove the existing product package from the Master Repository in ePO.
- Download the installer package from the Software Manager in ePO.
|
| New installation on a standalone Mac on or after August 14, 2017 |
You must download and use the new standalone installer from the Product Downloads site.
McAfee product software, upgrades, maintenance releases, and documentation are available from the Product Downloads site at: http://www.mcafee.com/us/downloads/downloads.aspx.
NOTE: You need a valid Grant Number for access. KB56057 provides additional information about the Product Downloads site, and alternate locations for some products. |
| McAfee Agent |
No action is required for existing MA installations; there is no security impact, and no functional impact. The certificate remains valid for functionality and security purposes.
McAfee recommends that new MA installs on Mac OS X also install MA 5.0.6 Hotfix 11211288, because this has been updated with the new signing certificate. |
NOTES:
- ePO Cloud has already been updated with the packages signed with the new Apple developer certificate. ePO Cloud users should not experience any installation failures.
- Hotfixes have been released for most of the products, with exception to FRP and MNE, where a repost has been undertaken and the affected components re-signed with the new certificate.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Behavior observed when old packages are used for standalone installation / ePO deployment:
- During a standalone installation with an older package, a pop-up message will be displayed to the user stating that the certificate has expired; however, the user will be able to proceed with the installation.
- ePO deployments with older packages will fail. No pop-up message will be displayed on the local client.
