public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: nisus@redchan.it
To: "Paul G. Allen" <pgallen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, tytso@mit.edu
Subject: Re: Yes you have standing to sue GRSecurity - Yes there is a blatant violation
Date: Sun, 30 Jul 2017 10:15:44 +0000	[thread overview]
Message-ID: <9787feb121bbbfc8035382e8bdd301b1@redchan.it> (raw)
In-Reply-To: <d4625c58917b05b4b37b9e6e66c5bc23@redchan.it>

Or as Bruce Perens put it (and yes Bruce Perens is correct, and yes I am 
an attorney)

----------------
Bruce Perens wrote:

"Currently, Grsecurity is a commercial product and is distributed only 
to paying customers. Under their Stable Patch Access Agreement, 
customers are warned that if they redistribute the Grsecurity patch, as 
would be their right under the GPL, that they will be assessed a 
penalty: they will no longer be allowed to be customers, and will not be 
granted access to any further versions of Grsecurity. GPL version 2 
section 6 explicitly prohibits the addition of terms such as this 
redistribution prohibition."

"By operating under their policy of terminating customer relations upon 
distribution of their GPL-licensed software, Open Source Security Inc., 
the owner of Grsecurity, creates an expectation  that the customer’s 
business will be damaged by losing access to support and later versions 
of the product, if that customer exercises their re-distribution right 
under the GPL license. Grsecurity’s Stable Patch Access Agreement adds a 
term to the GPL prohibiting distribution or creating a penalty for 
distribution. GPL section 6 specifically prohibits any addition of 
terms.  Thus, the GPL license, which allows Grsecurity to create its 
derivative work of the Linux kernel, terminates, and the copyright of 
the Linux Kernel is infringed. The GPL does not apply when Grsecurity 
first ships the work to the customer, and thus the customer has paid for 
an unlicensed infringing derivative work of the Linux kernel developers 
with all rights reserved.  The contract from the Linux kernel developers 
to both Grsecurity and the customer which is inherent in the GPL is 
breached."


perens.com/blog/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/

Stable patch agreement:
perens.com/wp-content/uploads/2017/06/grsecstablepatchaccessagreement_additionalterms.pdf

----------------

Again, Yes I am an attorney, yes Bruce Perens is correct, Yes I know 
what I'm talking about in this field more than you American Programmers, 
no you do not know what you are talking about if you have not studied 
law.

  reply	other threads:[~2017-07-30 10:15 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     ` Yes you have standing to sue GRSecurity - Yes there is a blatant violation nisus
2017-07-30 10:15       ` nisus [this message]
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=9787feb121bbbfc8035382e8bdd301b1@redchan.it \
    --to=nisus@redchan.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgallen@gmail.com \
    --cc=tytso@mit.edu \
    /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