No private keys were leaked; however a signed policy file, that lets you disable the protections within secureboot was discovered and repurposed. Its not so mu

No private keys were leaked; however a signed policy file, that lets you disable the protections within secureboot was discovered and repurposed. Its not so much a backdoor key, but an overly permissive mechanism within microsofts secureboot implementation that could be used to implement a backdoor within the system. A similar analogy in the CA world would be when the Microsoft Terminal Server Licensing CA (which accepted user submitted signing requests) was signing certificates that worked in other contexts (ie: https). This didn't break the CA system globally just one overly permissive implementation.