Asahi Linux Drops MIT and Goes Full GPL After Spotting LLM-Assisted License Laundering
7 190 It's FOSS reports: Asahi Linux is the reason you can run Linux on an Apple Silicon Mac today. For years, the project put most of its own code under the MIT license so that anyone, including the BSDs, could reuse it as needed... They have announced that Asahi is moving all of its repositories to the GNU General Public License version 2 or later. Going forward, all Asahi Linux code will be under strong copyleft licenses only.
Asahi Linux compares their dilemma to the 1990s, when "permissively licenced projects were viewed by tech companies as free real estate to pilfer and exploit," adding that "Those who do not learn from history are doomed to repeat it... The malicious practices of the 90s and 2000s have reared their ugly heads once again, this time driven in large part by both the insatiable appetite of frontier AI labs for high-quality training data, and militant animosity toward the Free Software community." In short, they argue that for Asahi Linux, using the permissive MIT license "is no longer viable." Some time ago, we were made aware of multiple attempts to exploit our permissive licensing to hijack our work, with a direct view to replacing the project and aggressively monetising Linux on Apple Silicon. In some extreme cases, in-development feature code was being lifted straight out of our personal forks and published without attribution or lazily rewritten with LLM assistance to obfuscate its origin. The MIT licence explicitly allows this, and has no carveouts to protect against bad faith actors. As such, we made the difficult decision to begin the process of transitioning all of our repositories to the GNU General Public License version 2 or later. Going forward all Asahi Linux code will be licenced under strong copyleft licences only.
It's FOSS explains that "Under the GPL, anyone who distributes a modified version has to release the source under the same license. You can't legally build a closed, paid Apple Silicon distro on top of GPL code. And if a product's source has to be public, the copying is easier to spot."
And their article also points out that before AI, bad actors attempting code laundering "usually meant manually rewriting code line by line, renaming variables and stuff, and shuffling functions around until it no longer looked like the original. LLMs made it much more easy and cheaper of course." In case you did not know, Asahi Linux forbids AI generated code contribution... As far as I can tell, this is the first time a major open source project has moved to copyleft specifically because of AI-assisted code laundering. Projects have relicensed before, but usually to stop cloud providers from reselling their work as a service. This one is specifically about AI...
The move has drawn criticism, particularly from the BSD side, which was one of the main reasons Asahi chose MIT in the first place. OpenBSD's Apple Silicon support relies on Asahi's m1n1 bootloader.
7 comments
Re:Uhh... Cool? (Score: 5, Insightful)
by phantomfive ( 622387 ) on Monday November 09, 2026 @12:53AM (#66416191)
If the resulting implementation looks too much like the original, then it will probably still count as a copyright violation in court. If you want to do a true clean-room implementation, then you need to keep the code out of the LLM's training data.
Re:Uhh... Cool? (Score: 5, Interesting)
by T34L ( 10503334 ) on Monday November 09, 2026 @01:12AM (#66416207)
The stupid little legal ritual you propose makes less and less sense as something that could become the accepted status quo when you realize it works just as well if a little more laboriously if the first step is done over a decompile of the software, perhaps in combination of letting the LLM just eat the documentation or perhaps experiment with the software in the process. Works with electronics to a pretty good degree, too.
We're sooner or later gonna have to deal with the fact that a LLM can just make a functioning (not necessarily good) copy of any software, open source or not. And if the legal precedent that this is a fair game holds, it's gonna be the inevitable death of Autodesk and Adobe and in the long long run, probably Microsoft and Oracle.
I personally could live with open source becoming a little more annoying if that's the cost of death of the whole current commercial software, particularly SaaS ecosystem, but I feel like the legal winds of what's derivative and what's protected intellectual property will still very well change, before all the behemoths bleed to death.
I keep hearing this but (Score: 5, Insightful)
by BitterEpic ( 10503015 ) on Monday November 09, 2026 @01:57AM (#66416247)
The license can be legally worked around:
1. Have one AI agent document the code fully by explaining how it works in plain english 2. Copy that new documentation to an entirely segregated second agent 3. Instruct the new agent to write brand new code according to the documentation
It's unlikely this will be done for all OSS projects since the result usually has bugs and inconsistencies. But spend a week or two doing passes over it for improvement and you get a functional reimplementation. (What license that can use will depend on how the law around AI code shakes out in the future)
I keep hearing this but... if the AI was already trained on the code I don't think this set of steps makes any sense. It isn't clean room regardless. If you remove the guardrails of whatever model you are using, I'm pretty sure you can get literal quotes of open source projects. Its all garbage all the way down enabled by the government allowing rapid IP infringement.
MIT vs GPL (Score: 5, Informative)
by phantomfive ( 622387 ) on Monday November 09, 2026 @12:55AM (#66416195)
If you want your code to be used as widely as possible, then use an MIT/BSD license.
If you want companies to give back if they use your code, then use GPL. If you want to dual license, then use GPL.
Both licenses are good, just use the right tool for the goal.
Re:MIT vs GPL (Score: 5, Insightful)
by dgatwood ( 11270 ) on Monday November 09, 2026 @03:36AM (#66416327)
The assumption that code will be more widely used if it's MIT licensed could at best be called wishful thinking, but is actually self delusion to justify irrational behavior. As MIT licenses provide no incentive to contribute back, your code is not going to attract as many contributors and thus become stale and less useful than copyleft licensed code.
Not really. MIT licenses might not give an incentive to contribute back, but most larger companies that use MIT-licensed code do, in fact, contribute back. By contrast, GPL v3 is so toxic that with the sole exception of my first tech employer (which was a Linux distro), no company I've ever worked at will touch it with a ten-meter pole.
Moreover, the GPL does not force you to give back, either. You can GPL something, and someone can use it indefinitely in a modified state without ever giving you the changes back. Someone can even create their own fork on GitHub and commit millions of changes and never send you a pull request or tell you that they did it. They have to give the source to their users, not yours. And this problem exists even in V3, and indeed, even in Affero V3.
So the notion that GPL somehow makes a project less stagnant is seriously wishful thinking. All the GPL does is eliminate most corporate contributors. The problem of getting people who change your code to actually give the code back to you in a usable form is exactly the same regardless of license.
Re:MIT vs GPL (Score: 5, Interesting)
by DamnOregonian ( 963763 ) on Monday November 09, 2026 @03:20AM (#66416309)
Sadly Linus Torvalds was one of the vocal opponents of GPLv3 because he fancied himself a startup millionaire (remember Transmeta [wikipedia.org]? Me neither.)
Oh, fuck you, buddy.
The fact that he disagreed with what GPLv3 was designed to fix- i.e., the inability for someone to cryptographically secure payloads on hardware that used his kernel, doesn't mean he disagreed with it "because he fancies himself a startup millionaire".
He wanted linux to be code-shared. He did not want it to be something that commercial entities wouldn't dare touch.
Do you feel like you're clever by trying to reduce the many arguments against the GPLv3 to that cheeky bullshit?
The neckbeards wanted his kernel under a licensing that fit their ideological beliefs- the problem is that Linux never shared those beliefs.
What followed was a change of the license to make a behavior they didn't like impossible, and a social pressure campaign to to move the kernel they pinched their nose and used (Hurd Hurd Hurd!) because they couldn't ever get theirs working (Hurd Hurd Hurd!) to a license they would have selected.
I, for one, am glad that Linux didn't go GPLv3. I wouldn't knock it if it had- after all, I didn't start that project. If it had- 90% of the devices that use linux today would be running VxWorks or QNX, and we would have gotten nothing in return, rather than source trees that add process support for 10 zillion arm variants- almost all contributed by manufacturers who were never going to give you the cryptographic signing keys for the devices they shipped.
does it matter? (Score: 5, Interesting)
by diffract ( 7165501 ) on Monday November 09, 2026 @04:47AM (#66416403)
AI is trained on copyrighted and pirated data, and I haven't seen anyone sue them and win. what difference would it make if they change the license? It would still be free real estate to AI companies