Well, that explains why my Oculus wasn't working tonight. I hope this ends up being as easy to fix as downloading a new binary.
All of Oculus’s Rift headsets have stopped working due to an expired certificate
31–40 of 390 posts
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#32Earlier quoted context omitted.
Because it was the certificate for the Windows driver, and Windows requires signed drivers.
The problem isn't that Windows requires drivers to be signed. The problem is that Windows allows drivers to have an expiration date. If Windows verifies a driver's signature at the time the driver is installed, the driver should be considered trustworthy for as long as it remains installed on that system. There's no reason to re-verify the signature every time the driver is used .
Perhaps as a malware defense?
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#33Earlier quoted context omitted.
The problem isn't that Windows requires drivers to be signed. The problem is that Windows allows drivers to have an expiration date. If Windows verifies a driver's signature at the time the driver is installed, the driver should be considered trustworthy for as long as it remains installed on that system. There's no reason to re-verify the signature every time the driver is used .
Perhaps as a malware defense?
Perhaps, but it would be better to trigger that with some knowledge of an attack, rather than at a fixed date.
[Edit: It may not be this simple. See the top-level comment by r1ch about timestamp servers.]
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#34Has anyone got a good way of managing certificates in the wild? With no real management and staff turnover I've seen a bunch of expired certificate problems. EDIT: presumably you need your client apps/libraries in the field write back when they use a cert that is <X months away from expiry.
I'd say someone very high up and "tied to the company", probably the CTO, should make sure a signing certificate is renewed when needed and make sure it's rotated every time it's about to hit expiration. For a company as big as oculus with the backing of Facebook, this is a pretty big issue.
I think the CTOs role here would probably be to make sure a process or team is in place to do this but not actually do it themselves? (For a company the size of oculus)
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#35This seems to be a somewhat common type of problem. I wonder if companies should routinely test on machines with the clock set one year into the future to catch them before they hit customers.
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#36Why is it possible for a device that is basically a display to stop working because a certificate expired? This future worries me.
It's more complex than a display; it's a display plus a collection of USB sensors and some low-level hooks into display management. This requires kernel-mode drivers, for good technical reasons, where a normal monitor wouldn't.
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#37Earlier quoted context omitted.
The problem isn't that Windows requires drivers to be signed. The problem is that Windows allows drivers to have an expiration date. If Windows verifies a driver's signature at the time the driver is installed, the driver should be considered trustworthy for as long as it remains installed on that system. There's no reason to re-verify the signature every time the driver is used .
Perhaps as a malware defense?
I think that's better handled through a Certificate Revocation List (CRL), especially in this case where's it's fairly easy to enforce and keep up to date.
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#38Earlier quoted context omitted.
Because it was the certificate for the Windows driver, and Windows requires signed drivers.
The problem isn't that Windows requires drivers to be signed. The problem is that Windows allows drivers to have an expiration date. If Windows verifies a driver's signature at the time the driver is installed, the driver should be considered trustworthy for as long as it remains installed on that system. There's no reason to re-verify the signature every time the driver is used .
Recommended practice is to timestamp windows drivers (and software) when they are signed. Without a timestamp, the driver is not trusted after the signing cert expires, which I guess is what happened here.
With a timestamp, as long as the signing date was within the signing cert's validity period, the signed driver continues to be trusted beyond the signing certificate expiration.
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#39Earlier quoted context omitted.
Because it was the certificate for the Windows driver, and Windows requires signed drivers.
The problem isn't that Windows requires drivers to be signed. The problem is that Windows allows drivers to have an expiration date. If Windows verifies a driver's signature at the time the driver is installed, the driver should be considered trustworthy for as long as it remains installed on that system. There's no reason to re-verify the signature every time the driver is used .
Stuxnet used malicious drivers signed with a stolen Realtek certificate.
Re: All of Oculus’s Rift headsets have stopped working due to an expired certificate
#40Why is it possible for a device that is basically a display to stop working because a certificate expired? This future worries me.
This is why I’m reluctant to shift completely to ebooks.