Mounir IDRASSI

Hello everyone, I just wanted to let you know that I have regained access to my Microsoft Partner Center account. Mr Scott Hanselman's intervention was key to getting this issue resolved and I am very grateful to him. A big thank you as well to the community whose support helped trigger widespread media coverage of this issue affecting me and other security projects. It feels good to see the positive power of social media in making our voices heard. Now I can finally prepare the long-overdue upcoming...

@hypernl: indeed, media coverage helped get Microsoft attention and also bring others to speak about this issue. Social media has a big power with this respect.

@withinrafael: Thank you for your proposal. Few hours ago I was contacted by a Microsoft VP (Scott Hanselman) following the media coverage. He connected me with the right people from Microsoft and hopefully things will be sorted out soon. I will share updates.

@geeivegotmail: Thank you for the feedback. Definitely media coverage helped to get Microsoft publicly communicate about this. Big thanks to the community for this.

@enigma2illusion: Thank you for the proposal. At the end, social media postings and interview with journalists helped trigger a response from Microsoft especially that other projects turned out to be affected. Microsoft VP Scott Hanselman reached out to help few hours ago. Hopefully it will be sorted out soon.

@phoenix-rising: there is no real secure solutions or workaround if Microsoft doesn't sign the driver or bootloader. Other solutions degrade Windows security and I will never recommend them: in such cases, it is better to move to another operating system like Linux.

@fzxx: We already have similar mechanism using GPG signatures. The issue here is that Microsoft holds the keys for SecureBoot on all the worlds PCs in addition to Windows driver signing keys so without their approval you are basically out of business!

@garymarks: Thank you for the feedback. Judging by the fact that other projects like WireGuard are affected, I don't think my move to Japan has anything to do with it. There seem to be an internal Microsoft policy that triggered this issue at large scale and there lack of communication and feedback made things worse. positive signs are coming...crossing fingers that it will be solved soon.