this post was submitted on 16 Jun 2024
1002 points (88.6% liked)

linuxmemes

20844 readers
2128 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 

Context:

Permissive licenses (commonly referred to as "cuck licenses") like the MIT license allow others to modify your software and release it under an unfree license. Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

Andrew Tanenbaum developed MINIX, a modular operating system kernel. Intel went ahead and used it to build Management Engine, arguably one of the most widespread and invasive pieces of malware in the world, without even as much as telling him. There's nothing Tanenbaum could do, since the MIT license allows this.

Erik Andersen is one of the developers of Busybox, a minimal implementation of that's suited for embedded systems. Many companies tried to steal his code and distribute it with their unfree products, but since it's protected under the GPL, Busybox developers were able to sue them and gain some money in the process.

Interestingly enough, Tanenbaum doesn't seem to mind what intel did. But there are some examples out there of people regretting releasing their work under a permissive license.

you are viewing a single comment's thread
view the rest of the comments
[–] pelya@lemmy.world 6 points 3 months ago (2 children)

Busybox was quickly replaced by BSD-licensed Toybox everywhere for that exact reason.

Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

This is false. It's perfectly legal to take GPL-licensed work, modify it, and sell it. As long as the work itself does not reach the general public, you don't need to release it's source code to the public (e.g. your work for the military, you take money for your work, and provide source code to them, but not release it publicly).

[–] brotundspiele@feddit.de 21 points 3 months ago (2 children)

Interesting point for the military: If you build a rocket that contains GPL software, and shoot the rocket towards your enemy, you are obliged to send another rocket containing the source code.

[–] Moorshou@lemmy.zip 3 points 3 months ago

This made me chuckle.

[–] Fedizen@lemmy.world 2 points 3 months ago

they'd have to sue you in court to get the second rocket.

[–] Adanisi@lemmy.zip 15 points 3 months ago* (last edited 3 months ago) (2 children)

Busybox is very much widely used though?

And how is it false that the GPL makes software remain free? Read the free software definition, it's about the freedom of users, not the freedom of people who aren't users (that doesn't really make sense). Free software isn't "source code available to general public even if they aren't users".

[–] renzev@lemmy.world 14 points 3 months ago

I think the confusion here is selling software vs distributing source code. Free software can be sold, as long as you provide the source code and don't try to stop others from redistributing copies for free. The busybox GPL lawsuits were about companies that redistributed busybox (or software built on top of busybox) without providing the source code. Whether or not they charged money for it isn't relevant.

[–] pelya@lemmy.world 2 points 3 months ago (1 children)

It's false that you cannot sell GPL-licensed work.

[–] Supermariofan67@programming.dev 3 points 3 months ago

Ok but I don't see how that was ever in dispute?