linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: voisinsdualice@8chan.co
To: linux-kernel@vger.kernel.org
Cc: rms@gnu.org, rohit@thelawfirm.io, contact@grsecurity.net
Subject: Bruce Perens - inconsistent statements regarding Copyright, GPL, Open Source Security.
Date: Wed, 24 Oct 2018 12:32:00 +0000	[thread overview]
Message-ID: <3a14b6f08c217a45957116fedc43e8eb@8chan.co> (raw)

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

In a prior public statement, Bruce Perens put forth a legal theory where 
users of a certain piece of Software would be liable for contributory 
copyright infringement*[1]. This statement, specifically the 
pronouncement of such damages reachable, is predicated on a pure 
copyright License theory regarding the grant under-which the Linux 
Kernel is distributed and modified.

* 
(https://perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/ 
)

As we all know, under a contract theory, damages are quite limited 
regarding opensource licenses** (See the initial district court 
determination of Jacobsen v. Katzer) and the legal theory published by 
Bruce Perens, if analyzed under a contract theory regarding the GPL 
would become a less-than-likely scenario.

** (For this very reason, the FSF specifically drafted version 2 of the 
GPL to avoid language that would tend to induce a contract reading 
rather than a bare license construction. The FSF has maintained for 
decades that the GPL is a bare license and is not a contract)

It is just that utterance, added by Bruce Perens, regarding contributory 
copyright infringement damages reachable vis a vis the GPL version 2, 
that induced upwards of 70 of Open Source Security's clients to cease 
their business dealings with Open Source Security.

Bruce Perens has recently made known, publicly, that he currently 
believes in a Contract theory regarding the GPL version 2, specifically 
regarding the Linux Kernel. He has stated that he, infact, in the past 
has supplied expert testimony praying to the court for it to find that 
the GPL is, in fact, a contract (and not a bare (copyright) license). He 
has stated that the court has indeed relied on his testimony in various 
pleadings. ***[3]

Here, ( 
https://developers.slashdot.org/comments.pl?sid=12767438&cid=57489528 ) 
Bruce Perens argues that case law has overridden the esteemed Raymond 
Nimmer's opinion that the GPL is not a contract and is, at best, a 
failed contract, and likely a bare license akin to a property license. 
Bruce Perens further clarifies that it was his very own testimony that 
has convinced the court that the GPL is infact not a bare license and is 
instead a contract.

If these pleadings were to have occurred prior to the theory published 
regarding Open Source Security and its Contributor Access Agreement, 
that would put the lie to any suggestion that Bruce Perens in fact 
believed in the theory that he published at the time of publication and 
would instead suggest that rather than proffering his opinion regarding 
a matter - he was instead intentionally publishing a theory he believed 
to be a lie in-order to harm Open Source Security - A goal that has 
indeed been effected (specifically by the "Contributory Copyright 
Infringement" addendum).






*[1]
-------
https://perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/
Posted on June 28, 2017 by Bruce
Warning: Grsecurity: Potential contributory infringement and breach of 
contract risk for customers




***[3]
-------
https://developers.slashdot.org/comments.pl?sid=12767438&cid=57489528
-------

Re:Who gives a FUCK about Nimmer? (Score:2)
by Bruce Perens ( 3872 ) <bruce@perens.com> on Tuesday October 16, 2018 
@09:10PM (#57489528) Homepage Journal

If lawyers were never wrong, we'd have no need for courts. Which means 
they're wrong half the time, or at least the adopt unsupportable 
arguments half of the time.

Case law has overridden him on the GPL question, thanks in part to my 
pro-bono testimony. But courts and lawyers still take him seriously. And 
me, sometimes.

-------

In response to:

> Who gives a FUCK about Nimmer? (Score:0)
> by Anonymous Coward on Tuesday October 16, 2018 @08:30PM (#57489396)
> 
> Who gives a FUCK about Nimmer?
> 
> He said the GPLv2 was "not a contract" - was "at best" "a failed 
> contract" - "has no consideration" - and thus it is a bare license 
> revocable by >the grantor.
> 
> Free Software has REJECTED this CLOWN Nimmer.
> Thus he is wrong.
> 
> http://illinoisjltp.com/journal/wp-content/uploads/2013/10/kumar.pdf
> http://oxwugzccvk3dk6tj.onion/tech/res/987076.html
> ...


[-- Attachment #2: bruce-perens-on-gpl-contract-vs-license.jpg --]
[-- Type: image/jpeg, Size: 216068 bytes --]

             reply	other threads:[~2018-10-24 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 12:32 voisinsdualice [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-19  1:24 Bruce Perens - inconsistent statements regarding Copyright, GPL, Open Source Security voisinsdualice

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=3a14b6f08c217a45957116fedc43e8eb@8chan.co \
    --to=voisinsdualice@8chan.co \
    --cc=contact@grsecurity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rms@gnu.org \
    --cc=rohit@thelawfirm.io \
    /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).