Loading story…
FreeBSD has removed its remaining GNU subtree from FreeBSD-CURRENT, advancing a long-running effort to eliminate GPL-licensed components from the operating system’s base system ahead of FreeBSD 16. A source commit titled "Retire the GNU subtree" followed earlier work to retire dialog, and project reporting said the development branch had already been replacing GPL-licensed tools such as diff3 and GNU dialog with BSD-licensed alternatives.
The replacements include an OpenBSD-derived diff3 and FreeBSD’s own bsddialog, which has matured enough to support functionality needed by utilities such as dpv. The change reflects FreeBSD’s broader strategy of reducing dependence on GNU code—particularly GPLv3 software—by substituting BSD-licensed implementations and LLVM-based tooling, with FreeBSD 16 expected to ship without GPL-licensed components in the base system.
See the reporting duties and controls this puts on the clock.
1 event from the most recent confirmed update back to the earliest known activity.
A FreeBSD source repository commit titled "Retire the GNU subtree" was authored by des, marking removal of the GNU subtree from FreeBSD-CURRENT as part of the project's effort to eliminate GPL-licensed components from the base system. The commit references Differential Revision D55425 and follows an earlier parent revision related to retiring dialog.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See what this changes for your reporting obligations and which controls it puts on the clock.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
