mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "Paul G. Allen" <pgallen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Yes you have standing to sue GRSecurity
Date: Sat, 29 Jul 2017 22:55:22 -0700 (PDT)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1707292253110.3788@qynat-yncgbc> (raw)
In-Reply-To: <CAN4-gUGQJCdYysoxE6=6uU8NS0b-Nkr-vr9AQ7bSmwddmf95GQ@mail.gmail.com>

On Sat, 29 Jul 2017, Paul G. Allen wrote:

>> It's not even clear that there is infringement.  The GPL merely
>> requires that people who have been distributed copies of GPL'ed code
>> must not be restricted from further redistribution of the code.  It
>> does not require that that someone who is distributing it must
>> available on a public FTP/HTTP server.

what I have seen reported is that they are adding additional restrictions, that 
if any of their customers redistribute the source, their contract with 
grsecurity is terminated.

> If there is something to this (that GRSecurity is somehow in violation
> of the GPL), then it would probably be a very good idea for someone
> (the community, Red Hat, etc.) to protect the kernel. From my
> understanding, at least in America, protections under any license or
> contract (especially dealing with copyright and trademark
> infringement) are only enforceable as long as the party with the
> rights enforce the license/contract/agreement.

You are thinking of Trademarks, they must be defended or you loose them. 
Contracts and Licenses do not need to be defended at every chance or risk 
loosing them.

> There is also something in law called "setting a precedent" and if the
> violating of the Linux license agreement is left unchecked, then quite
> possibly a precedent could be set to allow an entire upstream kernel
> to be co-opted.

This is a potential problem.

David Lang

  reply	other threads:[~2017-07-30  6:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-29 13:06 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 [this message]
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
2017-07-30 15:18         ` Mike Galbraith
  -- strict thread matches above, loose matches on Subject: below --
2017-07-29 12:30 Yes you have standing to sue GRSecurity nisus

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=nycvar.QRO.7.76.6.1707292253110.3788@qynat-yncgbc \
    --to=david@lang.hm \
    --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®