public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: David Lang <david@lang.hm>
Cc: "Paul G. Allen" <pgallen@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Yes you have standing to sue GRSecurity
Date: Sun, 30 Jul 2017 11:47:42 +0200	[thread overview]
Message-ID: <20170730094742.GD18381@amd> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1707292253110.3788@qynat-yncgbc>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

On Sat 2017-07-29 22:55:22, David Lang wrote:
> 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.

Question is if this is legal thing to do.

Because if it is, there could be other "more interesting" abuses of
the GPL (*), and we may want GPLv4 to fix it.

									Pavel

(*) Such as: you give us million dollars. You are free to distribute
the sources under the GPL, but if you do, our contract ends and we
will not be returning the million.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2017-07-30  9:47 UTC|newest]

Thread overview: 13+ 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         ` Pavel Machek [this message]
2017-07-30  9:47       ` Yes you have standing to sue GRSecurity 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=20170730094742.GD18381@amd \
    --to=pavel@ucw.cz \
    --cc=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