Dan Čermák

@Defolos
219 Followers
262 Following
1.5K Posts
[PATCH] execve: block Emacs binaries

@goodmirek Not sure, but we suspect the RAM chip is broken. Or we just got unlucky with a faulty NVMe and a faulty USB drive
@xenodium Please make this a thing 🙏
@larsmb Oder uns gegenseitig wegbomben. Oder uns die Kehle aufschneiden, weil wir an die falschen imaginären Freunde glauben. Die Liste ist schier endlos 😕
it's not the NVME... even a live system dies with squashfs errors
That feeling when you come to a conference, and the demo system's NVME disk immediately dies 🫠
Love to see that Virgin UK/O2 have blacklisted "http://detectportal.firefox.com/canonical.html" (the URL Ffox uses to invoke a captive portal, such as the ones you have to clear in order to use public hotspots with Virgin as a provider). Also nice to see that they've copyrighted the error page.
@kattascha was ist das neue Notebook?
A man used LLMs to generate hundreds of thousands of "songs", then used bots to stream them billions of times, to collect $8m in royalties. https://www.justice.gov/usao-sdny/pr/north-carolina-man-pleads-guilty-music-streaming-fraud-aided-artificial-intelligence-0 Is there a better metaphor for late-stage capitalism than burning resources to make songs that are never listened to, then steaming them to robots that will never hear them, ad infinitum?

The open source vulnerability scanner trivy has experienced a *second* security incident: a compromised release (v0.69.4) was published to the trivy repository.

https://www.stepsecurity.io/blog/trivy-compromised-a-second-time---malicious-v0-69-4-release

Trivy Compromised a Second Time - Malicious v0.69.4 Release, aquasecurity/setup-trivy, aquasecurity/trivy-action GitHub Actions Compromised - StepSecurity

On March 19, 2026, trivy — a widely used open source vulnerability scanner maintained by Aqua Security — experienced a second security incident. Three weeks after the hackerbot-claw incident on February 28 that resulted in a repository takeover, a new compromised release (v0.69.4) was published to the trivy repository. The original incident disclosure discussion (#10265) was also deleted during this period, and version tags on the aquasecurity/setup-trivy GitHub Action were removed. Trivy maintainers deleted the v0.69.4 tag and Homebrew downgraded to v0.69.3. The following is a factual account of what we observed through public GitHub data.