An AI Agent Filed a DMCA Takedown. The Rights Holder Had No Idea.

An unauthorized AI agent filed a DMCA (Digital Millennium Copyright Act) copyright takedown against gallery-dl, and the rights holder never approved it. Linux 7.0-rc7 confirms April 13 stable release.

An AI Agent Filed a DMCA Takedown. The Rights Holder Had No Idea.

👨🏻‍💻 My Today's Article

Ubuntu 26.04 LTS Breaks Backward Compatibility on Purpose

Ubuntu 26.04 LTS ships three changes that will break existing workflows on upgrade day

Medium Link | Canartuc.com Link


⚡ TL;DR

  • Linux 7.0-rc7 released April 6 with larger-than-usual patch set; Torvalds confirms stable 7.0 on track for April 13 release
  • Linux 6.6.133 reverts backporting mistake that removed xattr syscall safety validation, preventing kernel panics on invalid file descriptors
  • Intel i486 CPU support removal patch queued for Linux 7.1, ending 37 years of 486 compatibility in the kernel
  • gallery-dl migrates to Codeberg after DMCA takedown, with FAKKU CEO revealing the notice was filed by an unauthorized AI agent
  • Microsoft releases Agent Governance Toolkit (MIT license), the first toolkit addressing all 10 OWASP agentic AI risks with sub-millisecond policy enforcement

🏆 Top Story

Linux 7.0-rc7 Ships April 6, Stable Release Confirmed for Next Week

  • Linux 7.0-rc7 was released on April 6, 2026, with Linus Torvalds confirming the final stable release is on track for April 13. The patch set is larger than usual for an rc7, with approximately half consisting of driver updates (GPU, networking, USB). Memory safety fixes address use-after-free bugs and out-of-bounds reads. New security documentation targets AI-generated kernel bug reports. The docs give AI agents structured guidance for submitting vulnerability reports. Torvalds quipped about the Easter bunny in his release announcement. The unresolved PostgreSQL throughput regression on AWS Graviton4 (0.51x performance under PREEMPT_LAZY) remains unfixed, with no clean resolution expected before stable release. Ubuntu 26.04 LTS (April 23) and Fedora 44 (April 14) both depend on this timeline.
  • Source: Phoronix

An AI agent filed a copyright takedown against an open source project this week. The company whose name was on the notice had no idea it had happened.

Welcome back. Today: AI agents acting without permission. Linux is dropping support for a 37-year-old CPU. And a kernel backporting mistake that nearly crashed production servers.

I spent my weekend reading kernel mailing lists. You're about to benefit from that questionable life choice.

A company called FAKKU LLC filed a DMCA takedown against gallery-dl on March 23. Gallery-dl is an open source media downloader. The notice went through Remove Your Media LLC, a third-party service, and it targeted extractors for adult content sites.

GitHub gave the maintainer, mikf, seven days to comply. By March 28, nine extractors were removed and force-pushed. The repository got disabled.

Standard DMCA story so far. Open source project gets hit. Maintainer complies. Project moves.

But then the twist.

FAKKU's CEO came out and said the DMCA notice was sent by an AI-powered third-party agent, and here's the quote: "without our approval or permission."

The company whose name was on a legal document filed under penalty of perjury didn't authorize it. An AI agent did.

DMCA Section 512(c)(3) requires takedown notices to include a statement under penalty of perjury. Section 512(f) creates liability for knowing misrepresentation.

So if an AI agent generates and submits the notice on its own, who's accountable? The agent? The company that hired the service? The service that deployed the agent?

Mikf announced migration to Codeberg on April 5. The removed extractors are preserved there. Some folks on Hacker News pointed out that Codeberg is registered in Germany. German copyright law is actually stricter than the US DMCA in some respects. So the move isn't necessarily safer. It's just different.

Now, while AI agents were filing unauthorized legal notices, the Linux kernel had its own week.

Linux 7.0-rc7 shipped on April 6. Linus Torvalds confirmed the stable release is on track for April 13. That's one week from now.

The patch set was bigger than usual for an rc7. About half of it is driver updates: GPU, networking, USB. Memory safety fixes cover use-after-free bugs and out-of-bounds reads. And there's new security documentation specifically targeting AI-generated kernel bug reports.

But the PostgreSQL throughput regression persists. On AWS Graviton4 under PREEMPT_LAZY, PostgreSQL runs at half speed. 0.51x performance. Peter Zijlstra says PostgreSQL should adopt Restartable Sequences. Technically correct. Practically impossible before April 13.

So Ubuntu 26.04 LTS ships on April 23. Fedora 44 ships April 14. Both face the same choice: carry a downstream patch or pass that regression to users running PostgreSQL on ARM64.

Meanwhile, a quieter but scarier fix landed in Linux 6.6.133.

Greg Kroah-Hartman released it on April 6. It reverts a backporting mistake that removed safety validation for four extended-attribute syscalls: fgetxattr, flistxattr, fremovexattr, and fsetxattr.

What does that mean in plain terms? If you passed an invalid file descriptor to any of those syscalls, instead of returning a clean error code, your kernel could panic. Crash. Done.

Brad Spengler from grsecurity caught it. No CVE was assigned. If you're running production servers on the 6.6 LTS branch, update immediately.

And then there's the nostalgia story.

A patch from Ingo Molnar, one of the kernel's most prolific contributors, has been queued for the Linux 7.1 merge window. It removes support for Intel i486 CPUs.

That's 37 years of compatibility, gone. The M486, M486SX, and MELAN Kconfig options are getting removed. The new minimum CPU baseline will require Time Stamp Counter and CMPXCHG8B instruction support, features that 80486-family chips don't have.

Torvalds said he "really don't think i486 class hardware is relevant any more" and suggested using older kernels as, quote, "museum kernels."

This is the first processor architecture removal since 80386 support was dropped in 2012. No known Linux distribution still ships with i486 CPU support. But the compatibility code imposes real maintenance costs on developers who have to work around the limitations of hardware no one uses.

It's like keeping a parking space reserved for a car that was scrapped fifteen years ago. At some point, you just paint over the lines.

All of these stories connect to the same gap.

Microsoft released the Agent Governance Toolkit on April 2. It's open-source, MIT-licensed, with seven packages across Python, Rust, TypeScript, Go, and .NET.

The core component, Agent OS, is a stateless policy engine that intercepts every agent action before it is executed. p99 latency sits below 0.1 milliseconds.

It's the first toolkit to address all 10 OWASP Top 10 risks for Agentic Applications, published in December 2025. Goal hijacking, tool misuse, identity abuse, memory poisoning, cascading failures, rogue agents.

Rogue agents.

Like the one that filed a DMCA notice without anyone knowing.

Now zoom out. The TeamPCP supply chain campaign has been running for weeks. Their CISA KEV remediation deadline for the Trivy compromise is tomorrow, April 8. They've shifted to credential monetization, working through roughly 300 GB of stolen credentials. The European Commission, Sportradar, Mercor AI, and over a thousand SaaS environments are affected.

And how did it start? Compromised tools acting with inherited permissions. Nobody asked whether those tools should still have access.

The missing column here is authorization.

Not capability. Not speed. Not whether AI agents can do things. Whether they were allowed to.

The DMCA agent had the ability to file a takedown request. It was never authorized. The compromised Trivy scanner had the capability to run in CI/CD pipelines. Nobody revoked its access when it was compromised. Microsoft's governance toolkit exists because the industry recognized this gap.

And that gap is everywhere. Five open source MCP gateways are competing to define how AI agents discover and invoke tools. IBM ContextForge, MCPJungle, Docker, Microsoft, MCPX. Same pattern as the 2015 API gateway wars. Centralized proxy. Authentication. Rate limiting. The winner will be decided by the distribution method, not the features.

🤓 I'll be checking whether my CI/CD scanner was authorized to perform half of what it did last Tuesday. Spoiler: it wasn't.

Free to read every morning. Or go paid. Less than a parking ticket in Munich a month.

I'll see you next time.

🧩 Open Source News

  • FAKKU LLC filed a DMCA takedown against gallery-dl on March 23 via Remove Your Media LLC. The notice targeted extractors for adult content sites. GitHub gave maintainer mikf a 7-day compliance deadline. By March 28, nine extractors were removed and force-pushed. The GitHub repository is currently disabled. FAKKU's CEO later disclosed the DMCA notice was sent by an AI-powered third-party agent "without our approval or permission," a case that raises questions about automated DMCA enforcement without human authorization. Mikf announced migration to Codeberg on April 5-6, where the removed extractors are preserved. Hacker News discussion noted Codeberg (registered in Germany) may offer limited additional protection since German copyright law is stricter than US DMCA provisions in some areas. The incident points to a new category of legal risk: AI agents autonomously filing copyright claims without the rights holder's knowledge.
  • Source: GitHub Discussion | Hacker News | Codeberg

Microsoft Releases Agent Governance Toolkit: First Open Source Framework Covering All 10 OWASP Agentic AI Risks

  • Microsoft released the Agent Governance Toolkit on April 2, a seven-package, multi-language system (Python, Rust, TypeScript, Go, .NET) for runtime security governance of autonomous AI agents. Licensed under MIT. The core Agent OS package functions as a stateless policy engine that intercepts every agent action before execution. p99 latency sits below 0.1 milliseconds. It is the first toolkit to address all 10 risks from OWASP's Top 10 for Agentic Applications (published December 2025): goal hijacking, tool misuse, identity abuse, memory poisoning, cascading failures, and rogue agents among them. Microsoft intends to move the project into a foundation for community governance. Available on GitHub and PyPI.
  • Source: Microsoft Open Source Blog | GitHub

Google Gemma 4 Ships Under Apache 2.0, First OSI-Approved Gemma License

  • Google released Gemma 4 on April 2 with four model sizes: E2B (2.3B), E4B (4.5B), 26B MoE (3.8B active/26B total), and 31B Dense. This is the first Gemma release under the Apache 2.0 license (previous versions used a custom restricted license Google could update at any time). The 31B Dense ranks #3 globally on LMArena's text leaderboard, above every commercial model except two. AIME 2026 math: 31B scores 89.2%. LiveCodeBench coding: 31B scores 80.0%. All models support native vision, audio, and 140+ languages. Total Gemma downloads exceed 400 million with 100,000+ community variants. The licensing shift puts Gemma on identical ground as Qwen (Apache 2.0) and more permissive than Meta's Llama (custom license with commercial restrictions).
  • Source: Google Blog

Open Source MCP Gateways: Five Projects Compete to Become the Agent Infrastructure Layer

  • Five open source MCP (Model Context Protocol) gateways are competing to define the agent infrastructure layer. IBM ContextForge (Apache 2.0, 3,500+ GitHub stars) federates MCP, A2A, and REST/gRPC endpoints with 40+ plugins and OpenTelemetry observability. MCPJungle (Go, ~952 stars) offers self-hosted enterprise mode. Docker MCP Gateway provides fully open source container isolation with auto-discovery. Microsoft MCP Gateway targets Kubernetes-native deployments with Azure Entra ID and StatefulSets. MCPX/Lunar.dev adds tool-level RBAC with ~4ms p99 latency and immutable audit trails (though not fully open source). The pattern: agent orchestration is shifting from application-level code to infrastructure-level gateways. API management followed the same trajectory a decade ago.
  • Source: Getmaxim.ai | BishopWCMartin

OpenObserve: Rust-Built Observability Platform Claims 140x Lower Storage Costs

  • OpenObserve, a Rust-built open source observability platform, uses Apache Parquet columnar storage with approximately 40x compression to claim 140x lower storage costs compared to Elasticsearch and Splunk. The platform ships as a single binary and can be operational in under two minutes. Recent engineering work includes rewriting their XDrain log pattern extraction algorithm from Python to Rust, achieving 361,000 log lines per second (roughly 40x improvement over the Python implementation). An AI SRE agent assists with problem identification. Log pattern recognition compresses millions of log lines into approximately 100 representative patterns. The project positions itself as a Datadog alternative for organizations unwilling to pay SaaS observability pricing.
  • Source: GitHub | PrismNews

GuppyLM: An 8.7M Parameter LLM That Teaches How Transformers Work

  • GuppyLM is a tiny language model (8.7M parameters, MIT licensed) built entirely from scratch to demystify transformer architecture. The model uses 6 layers, 384 hidden dimensions, 6 attention heads, a 4,096 BPE vocabulary, and a 128-token context window. Trained on 60,000 synthetic conversations across 60 topics. No GQA, no RoPE, no SwiGLU, no early exit. As simple as the architecture gets. A browser demo runs via WASM with a quantized ONNX model (~10MB). The entire training pipeline (data generation, tokenizer, model, training loop, inference) runs in a single Google Colab notebook in five minutes. Built for education, not production.
  • Source: GitHub | HuggingFace | Hacker News

LVFS Begins Over-Quota Warnings and API Limits for Non-Sponsoring Hardware Vendors

  • The Linux Vendor Firmware Service (LVFS) began enforcement actions on April 1 to encourage hardware vendors to contribute financially. Firmware pages for vendors exceeding 50,000 monthly downloads now display over-quota warnings. Access to custom API endpoints and automated upload frequency is limited for vendors below the "Startup" sponsorship tier. Sponsorship costs: $10,000/year for companies under 99 employees, $100,000/year for larger organizations (or employ an engineer working full-time on LVFS/fwupd). The free "associate" tier retains 50,000 monthly downloads and 50 monthly uploads. Approximately 140 OEMs and ODMs use the service; most should see no changes. The actions reflect an ongoing sustainability challenge: LVFS supports firmware updates across the Linux ecosystem but has historically been underfunded relative to its infrastructure costs.
  • Source: Phoronix | OMG! Ubuntu

🐧 Linux News

Linux 6.6.133 Reverts Backporting Mistake That Could Cause Kernel Panics on xattr Syscalls

  • Linux 6.6.133, released April 6 by Greg Kroah-Hartman, reverts a backporting error that removed safety validation on four extended attribute syscalls: fgetxattr, flistxattr, fremovexattr, and fsetxattr. The removed checks allowed invalid file descriptors to cause kernel panics instead of returning EBADF. Brad Spengler (grsecurity) highlighted the flaw. No CVE was assigned. The fix restores the original safety checks that prevent kernel crashes when automated scripts or applications pass invalid file handles during xattr operations. Anyone running production servers on the 6.6 LTS branch should update immediately.
  • Source: LinuxCompatible

Intel i486 CPU Support Removal Patch Queued for Linux 7.1, Ending 37 Years of Compatibility

  • A patch authored by veteran kernel developer Ingo Molnar has been queued into the tip/tip.git development branch for the Linux 7.1 merge window. It removes the M486, M486SX, and MELAN Kconfig options, preventing new upstream kernels from being configured for i486-class hardware. The new minimum CPU baseline will require Time Stamp Counter (TSC) and CMPXCHG8B instruction support, features absent in 80486-family chips. Torvalds stated he "really don't think i486 class hardware is relevant any more" and suggested using older kernels as "museum kernels." This is the first processor architecture removal since 80386 support was dropped in 2012. No known Linux distribution still ships with i486 CPU support. The compatibility code creates unnecessary maintenance burden for developers.
  • Source: The Register | Tom's Hardware

RHEL Extended Life Cycle Premium: 14-Year Support for Change-Averse Workloads

  • Red Hat announced RHEL Extended Life Cycle Premium on April 2, a standalone subscription extending RHEL major version lifecycle from 10 to 14 years. Even-numbered minor releases (e.g., RHEL 9.2, 10.2) receive six years of extended maintenance. Coverage targets Critical and Important CVEs (CVSS 7.0+). Includes 24x7 support with unlimited incidents. The subscription consolidates previously fragmented extended support add-ons into a single offering. Target customers: finance, healthcare, and government organizations where frequent minor release upgrades introduce operational risk and certification costs. For organizations running decade-old RHEL systems in regulated environments, this formalizes what was previously achieved through expensive, ad-hoc extended support arrangements.
  • Source: Linuxiac | Help Net Security

SUSE Ships Live Kernel Patches Across SLES 15 SP4-SP7, SLE Micro 6.0, and openSUSE Leap 16.0

  • SUSE released an active wave of kernel and real-time kernel live patches covering SLES 15 SP4 through SP7, SLE Micro 6.0, and openSUSE Leap 16.0. CVEs addressed include: CVE-2025-38488 (SMB client use-after-free), CVE-2025-40258 (MPTCP race condition), CVE-2025-40284 (Bluetooth MGMT timer), CVE-2025-40297 (net/bridge use-after-free), CVE-2025-68284 and CVE-2025-68285 (libceph out-of-bounds write and use-after-free), and CVE-2025-68813 (IPVS null pointer dereference). All rated Important. Live patching enables fixes without reboot, critical for production systems that cannot tolerate downtime windows.
  • Source: SUSE Support | LinuxSecurity

Fedora 44 Stable Release One Week Away, April 14 Target Holds

  • Fedora 44 remains on track for April 14 stable release. The beta shipped with Linux 6.19; the stable release may ship with Linux 7.0 if it reaches stable by April 12-13. Key components: GNOME 50, KDE Plasma 6.6 with the new Plasma Login Manager, Mesa 26.0, DNF5, GCC 16, LLVM 22, Ruby 4.0, Go 1.26, PHP 8.5, Django 6, and NTSYNC for improved Wine/Steam gaming. The Budgie spin migrates from X11 to Wayland. The Fedora Games Lab spin switches from Xfce to KDE Plasma. Enhanced ARM/aarch64 out-of-the-box compatibility. With Linux 7.0 stable now expected April 13, Fedora's April 14 timeline looks achievable.
  • Source: Fedora Project

TeamPCP Campaign: CISA KEV Deadline in 24 Hours, No New Compromises in 11 Days

  • The TeamPCP supply chain campaign's supply chain pause extends to approximately 11 days (no new package compromises since the Telnyx PyPI disclosure on March 27). The CISA Known Exploited Vulnerabilities (KEV) remediation deadline for CVE-2026-33634 (Trivy compromise) is April 8, one day away. The campaign remains in monetization phase: TeamPCP continues working through approximately 300 GB of stolen credentials, collaborating with the LAPSUS$ extortion group. Total confirmed blast radius: European Commission AWS (340 GB exfiltrated), Sportradar AG (26,000 users, 328 API key pairs), Mercor AI (4 TB), and 1,000+ SaaS environments (Mandiant estimate). Mandiant and Unit42 assess the supply chain pause should not be interpreted as campaign conclusion, as stolen credentials could enable future compromises at any time.
  • Source: Medium | Canartuc.com Article | Canartuc.com Newsletter

Manjaro Governance Crisis: 5th Week, No Resolution

  • The Manjaro governance standoff enters its eighth week. No new statements from Philip Müller or the 19 manifesto signatories. No fork announced. No nonprofit formation timeline proposed. Technical operations continue normally: stable and unstable updates ship on schedule. Müller's March 19 statement that he was "open to serious discussions" but only after a nonprofit was set up created a deadlock: the signatories want governance reform before forming the entity, and Müller wants the entity formed before discussions begin.

Subscribe to Can Artuc

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe