From: nipponmail@firemail.cc
To: linux-kernel@vger.kernel.org
Subject: Re: Will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)?
Date: Mon, 04 Nov 2019 17:56:32 +0000 [thread overview]
Message-ID: <f2f8761cb462b2576696c500cc57e257@firemail.cc> (raw)
In-Reply-To: <E1iRgHg-0007e0-Gd@fencepost.gnu.org>
You are incorrect. GPL version 2 section 6 states that one shall not add
additional restrictions between the agreement between the licensee and
further licensees. It governs that relationship vis-a-vis the protected
Work.
GrSecurity has, indeed, stipulated an additional restrictive term.
From: You may distribute derivative works freely.
GrSecurity has forced customers to agree to: We shall not distribute the
(non-separable) derivative work EXCEPT to our own customers (when
required).
That is clearly an additional restrictive term.
Yes, I am a lawyer. A court would not be "tricked" by GrSecurity putting
it's additional restrictive term in a separate writing. The license is
instructions about what you are allowed to do with Copyright Holder's
work; He EXPLICITLY forbade additional restrictive terms.
GrSecurity does not have a pre-existing legal right to create
non-separable derivative works at all. The default rights are: nothing
(all rights reservered).
On 2019-11-04 17:36, ams@gnu.org wrote:
> One is not under obligation to guarantee that new versions are
> distributed to someone, which also means obligations can be terminated
> for any reason. So while grsecurity might not be doing the morally
> and ethically right thing, I do not think they are violating the GNU
> GPL. You're still free to redistribute the patches, but grsecurity
> isn't under obligation to give you future updates.
>
> Their agreement text is located at
> https://grsecurity.net/agree/agreement_faq
next parent reply other threads:[~2019-11-04 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b0668893d6fbfeca10a724e1c5846e92@firemail.cc>
[not found] ` <E1iRgHg-0007e0-Gd@fencepost.gnu.org>
2019-11-04 17:56 ` nipponmail [this message]
2019-11-04 17:58 ` Will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)? - BP and EFF have addressed nipponmail
2019-11-04 18:20 ` Will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)? - He is violating, but you can also rescind the license nipponmail
[not found] ` <2fbd35b601c740b3cf88b73df7a2c123@firemail.cc>
[not found] ` <87ftj3gx9h.fsf@mid.deneb.enyo.de>
2019-11-05 0:37 ` Will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)? nipponmail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2f8761cb462b2576696c500cc57e257@firemail.cc \
--to=nipponmail@firemail.cc \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).