All of Oculus’s Rift headsets have stopped working due to an expired certificate

Re:All of Oculus’s Rift headsets have stopped working due to... by tallanvor on Thursday March 08, 2018 @05:32AM (#16543536)

I guess I can see reasons why some companies may want to be able to produce time-limited drivers:

Maybe they want beta versions to stop working, forcing users to upgrade.

For offline computers, it might be that some companies would see this as a way to enforce contract periods (customers would have to install an update to continue using the product when their contract is renewed).

Of course, disabling driver signature verification is still a way to bypass that, but often times the companies that do things like this probably aren't thinking about that.

[ Parent | on HN ]

Re:All of Oculus’s Rift headsets have stopped working due to... by mathieubordere on Thursday March 08, 2018 @06:34AM (#16543728)

Maybe the API should then explicitly ask for a 'timestamp-none' in case the driver needs to be time-limited, forcing the developer to at least think about it.

[ Parent | on HN ]

Re:All of Oculus’s Rift headsets have stopped working due to... by marcosdumay on Thursday March 08, 2018 @07:18AM (#16543878)

Do you have any reason that is good from the point of view of the computer owner? (You know, the one sending money to Microsoft.)

[ Parent | on HN ]

Re:All of Oculus’s Rift headsets have stopped working due to... by sleepybrett on Thursday March 08, 2018 @02:00PM (#16546685)

Then they can write it into the driver "Stop working on jan 1 2019"

[ Parent | on HN ]