Jay, I noticed this as well... There appears to have been a switch to a new intermediate certificate authority (CA) at Intel... So they have valid ceritificates, but they're signed by an intermediate CA that isn't recognized by some systems. Some systems - Mac OS and Windows - recognize this CA, and some Linux systems (like I have on my desktop) do not recognize it. Here's the details of that intermediate CA: CN = Intel External Basic Issuing CA 3A O = Intel Corporation L = Santa Clara ST = CA C = US If you dig through the certificate authorities your machine recognizes, you'll probably find this isn't in them. It isn't on at least some of our Linux desktops, but it is on Macs, and according to the trust chain on the Mac, it's valid and signed by one of the core root CAs. This might be because it's a newer intermediate CA and a system update will take care of it? I'm a little unsure of how awareness of intermediate CAs is handled - I had thought it was automatic because the certs were signed by root CAs, but perhaps it usually comes in an OS/manual update like root CAs. Since it's a valid CA, I'm not sure Intel can do anything to help. - Patrick Farrell On 03/12/2014 04:26 PM, Jay Lan wrote:

The issue should be resolved now. We apologize for any disruption this may have caused. j On Wednesday, March 12, 2014 13:44:20 Joshua J. Kugler wrote: -- Dev/Ops Lead High Performance Data Division (formerly Whamcloud) Intel