From: nisus@redchan.it
To: "Paul G. Allen" <pgallen@gmail.com>, nisus@redchan.it
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Yes you have standing to sue GRSecurity - Yes there is a blatant violation
Date: Sun, 30 Jul 2017 10:09:04 +0000 [thread overview]
Message-ID: <d4625c58917b05b4b37b9e6e66c5bc23@redchan.it> (raw)
In-Reply-To: <20170729200726.6qxlnh7mmfpfxkq3@thunk.org>
On 2017-07-29 20:07, Theodore Ts'o wrote:
> It's not even clear that there is infringement. The GPL merely...
Yes it is.
Here's a posting from before that explains it:
----------------
GPL v2
Section 6 states simply
"You may not impose any further restrictions on the recipients' exercise
of the rights granted herein."
From GRSecurity's "Stable Patch Agreement":
"Notwithstanding these rights and obligations, the User acknowledges
that redistribution of the provided stable patches or changelogs outside
of the explicit obligations under the GPL to User's customers will
result in termination of access to future updates of grsecurity stable
patches and changelogs."
Clear as day. What some lay people do not understand is that the terms
in section 6 are governing what agreements and actions the distributee
can take regarding furthur distributees, in reality, in the flesh.
Here the ACTIONS of GRSecurity are to RESTRICT the exercise of the
redistribution rights of the further distributee.
This is an action prohibited by the terms offered by the linux-rights
holders, and they have written as another term that the permission they
give to use their property is revoked upon violation of their terms.
Very simple.
(Someone previously said on another thread:)
> And none are imposed. However, you are given the option to agree to
> them. Clear as day.
The proffering of the additional restrictive terms is in and of itself a
violation of section 2. You are holding the clients to an additional
restriction and enforcing this restriction via a threat to suspend
business relationships.
(YES YOU HAVE IMPOSED AN ADDITIONAL RESTRICTION)
----------------
Here's it put another way:
----------------
------------------------
Correction to common
programmer's misunderstanding
------------------------
They don't have to add a term to the GPL per-se as the GPL is not a
party to the agreement, it is "merely" the (not-fully integrated)
writing describing the license that the rights-holders have granted
GRSecurity et al.
That is: the GPL in-part describes the license grant that the linux
rights-holders have extended.
(There may be other parts described elsewhere, even verbally or through
a course of business dealings or relationship)
(Copyright law, being quite bare on it's own, often borrows much from
contract law)
Licensees must extend the same grant to Distributees, they cannot add an
additional term to that relationship.
GRSecurity has added such a term.
They did not pen it into the text of the GPL.
But, according to existing testimony they did make it clear that
redistribution will not be tolerated.
It is unknown if an electronic or hard copy of this additional term
controlling the relationship exists,
or whether it was a verbal agreement, or even some implicit
understanding. Any which way: it is a forbidden additional
term.
next prev parent reply other threads:[~2017-07-30 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 13:06 Yes you have standing to sue GRSecurity nisus
2017-07-29 15:32 ` Paul G. Allen
2017-07-29 20:07 ` Theodore Ts'o
2017-07-29 23:20 ` Paul G. Allen
2017-07-30 5:55 ` David Lang
2017-07-30 7:14 ` David C. Rankin
2017-07-31 14:46 ` Yes you have standing to sue GRSecurity - Two options that can be used in concert or separately nisus
2017-07-30 9:47 ` Yes you have standing to sue GRSecurity Pavel Machek
2017-07-30 9:47 ` Pavel Machek
2017-07-30 10:09 ` nisus [this message]
2017-07-30 10:15 ` Yes you have standing to sue GRSecurity - Yes there is a blatant violation nisus
2017-07-30 15:18 ` Mike Galbraith
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=d4625c58917b05b4b37b9e6e66c5bc23@redchan.it \
--to=nisus@redchan.it \
--cc=linux-kernel@vger.kernel.org \
--cc=pgallen@gmail.com \
/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
all inboxes | Powered by JetHome®