linux-kernel - Re: Transcend's "one of the most cavalier GPL violations in a long time"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+xJJ19v4hD0VX3g2qwGLAZax=ssW7YPdumK25vpGs=3eebCEg@mail.gmail.com>
Date:	Tue, 15 Oct 2013 09:48:49 +0200
From:	Mats Liljegren <liljegren.mats2@...il.com>
To:	Rogelio Serrano <rogelio.serrano@...il.com>
Cc:	Pavel Machek <pavel@....cz>,
	"luke.leighton" <luke.leighton@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Transcend's "one of the most cavalier GPL violations in a long time"

> I was led to believe this in the busybox list. maybe we are communally
> smoking the same stuff. Linux Kernel Developers would rather go on
> developing better code than waste time on enforcement. Some even think
> it is counter productive to adoption of linux.
>
> Transcend most likely knows this.
>
> You have a piece of code under the GPL and the majority of the
> copyright holders say they will not enforce it. Thats virtually public
> domain code. Thats why i stopped contributing to the linux kernel and
> opted to maintain a massive patch instead.

I think it is sad that you take this decision purely based on the fact
that by contributing to the Linux kernel you will not get help to
enforce the GPL license for your code.

I'm a little bit curious however: In what way do you now have better
ways to enforce the GPL license of your code now that you maintain a
massive patch? Is it that you never show it to the public?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/