News for hackers. Stuff that matters.
Re:All of Oculus’s Rift headsets have stopped working due to... by agar on Thursday March 08, 2018 @11:26PM (#16549783)
To be clear, I'm not arguing that old, already-installed drivers should fail if not countersigned. This seems like an extreme, and customer-unfriendly failure case. However, I am saying that this appears to be the default implementation of Windows 10 build 1607+.

I won't argue it's right or wrong, actually. It's a choice, with different threat models driving different conclusions. Defining the failure modes with respect to security risks is a fraught business, and I hope Microsoft put a great deal of thought into it and has far more visibility into the risks than I. But it's what they appear to do, and we live in their world.

I argued elsewhere (in a late, top-level comment somewhere) that - if this is Windows's failure mode - MS should provide tools for devs to integrate into their build process that flags risky or mis-configured signature scenarios. This is too complicated, and used by too many non-security experts, with extreme failure modes, for it to be half-ass-able or easily done wrong.

Re:All of Oculus’s Rift headsets have stopped working due to... by dlubarov on Friday March 09, 2018 @03:21AM (#16550451)
Thanks for clarifying; I didn't realize that was Windows' behavior.