Silence 🦇 🇺🇸

🚨 NOW: It’s still LIGHT outside here in Newark, and anti-ICE rioters are ALREADY physically fighting with ICE agents As I’ve been saying for days, this is ONLY GETTING WORSE. Agents need REINFORCEMENTS!

The dark aging added charm and flair. Just more fascist changes from the pedo Oompa Loompa Cheeto.

They really do just all interview each other 😂

We will no longer submit bugs we discover in Apple systems through Apple Bounty Program.

McDonald's all new drinks have gone viral with caffeinated Refreshers on the menu: - Mango Pineapple Refresher - Sprite® Berry Blast - Strawberry Watermelon Refresher - Orange Dream - Blackberry Passion Fruit Refresher - Dirty Dr Pepper®

‼️ After the MSRC blog post about Nightmare-Eclipse, researchers are coming forward with their own MSRC horror stories. The response from the security community isn't going Microsoft's way. As they’re not backing Microsoft. Gabriel Landau, a well-known Windows security researcher, says he reported a Device Guard bypass with a 90-day window. MSRC told him it met their bar and they'd fix it, then asked him to hold disclosure for extra months. He agreed on the condition they issue a CVE. They patched it silently, decided after the fact it "didn't meet the bar," and never issued the CVE. In his words: "MSRC strung me along for a few extra months to keep me quiet, then broke their word." Another researcher, rootsecdev, says he responsibly disclosed a legacy-auth flaw that allowed password spraying while avoiding smart lockout. Five months later, MSRC replied that it "doesn't meet the bar for servicing," silently fixed it, and closed the case. Microsoft's post was meant to defend their coordinated disclosure policy. Instead it became a thread of researchers explaining why they've stopped trusting their process.