Google Project Zero to Publicly Disclose Vulnerabilities 90 Days After Reporting

·1 views

Google's Project Zero security team has announced that it will publicly disclose software vulnerabilities 90 days after they are reported to vendors. The policy sets a fixed window for affected companies to address flaws before details become public. The announcement was shared on Hacker News, where it drew significant attention from the technology community. The source material provides limited detail beyond the policy timeline and the link to Project Zero's disclosure policy page.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

FBI Warns of North Korean 'FaceStealer' Scheme Using Fake Video Calls to Steal Crypto

The FBI reports that North Korean state-sponsored hackers are using compromised accounts and secretly recorded webcam footage to lure victims into fake video conferences. Participants are tricked into running commands or scripts under the pretext of fixing audio or connection problems, which installs malware that steals cookies, credentials, and cryptocurrency. The agency says more than $400 million was taken over the preceding 18 months and that over 900 webcam recordings were seized, though recordings do not equate to verified victims. Attackers reportedly reuse stolen contacts and footage for follow-on attacks, including an attempted compromise of a JavaScript library maintainer that was caught early. The FBI also notes other attempts targeting npm and Rust package maintainers, with no confirmed success.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google Play Console Guide Covers Every Dashboard Section for Developers

A new guide walks developers through the full Play Console account dashboard at play.google.com/console, which bundles release tracks, store listings, monetisation, policy declarations, quality monitoring, payments, and team administration. It explains that many developers only learn the launch-critical screens and discover the rest during problems such as policy warnings or payout delays. The guide details the All Apps home screen, including status badges and filtering, and recommends checking the per-app dashboard and the Inbox regularly. It also outlines the release tracks, covering internal, closed, and open testing, along with the production track and staged rollouts. Account registration details such as the fee and identity verification are referred to the Help Center rather than covered in depth.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Microsoft Outage Raises Questions on Reliance and Backup Plans for Organizations

A Microsoft outage prompted a discussion on how widely businesses depend on the company's services. The DEV Community post asks readers whether the disruption pushed them toward alternative apps or whether they were forced into switching. It also questions whether organizations have contingency plans ready for future failures. The article frames the outage as something that can stall a large share of the economy. The piece is presented as a community prompt for readers to share their own experiences.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Summarize Client Emails with Claude AI and Save Them to Notion Without Code

A tutorial shows how to have Claude AI automatically summarize incoming client emails and store the results in Notion. The workflow uses Make to watch a Gmail label called Clients and pass each new email's sender, subject, and body to Claude. Claude returns a three-line summary, action items, and a High, Medium, or Low priority, which Make maps into a Notion database. The database is organized by priority so urgent emails appear first, and the author demonstrates it with two dummy emails. The guide requires a Make account, a Claude API key, Gmail, and a free Notion account, and notes that some links are affiliate links.

0 comments Read more at DEV Community