From: gameonlinux@redchan.it
To: Jean Louis <bugs@gnu.support>
Cc: gnu-system-discuss@gnu.org, bruce@perens.com, rms@gnu.org,
esr@thyrsus.com, torvalds@linux-foundation.org, ams@gnu.org,
linux-kernel@vger.kernel.org
Subject: Re: (Censored) Why will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)?
Date: Sat, 02 Nov 2019 00:48:25 +0000 [thread overview]
Message-ID: <b07b73864b9e65d220437f38d7ad746e@redchan.it> (raw)
In-Reply-To: <20191101070258.GK3889@protected.rcdrun.com>
I have a law license, I don't need to read about who has standing to
sue, and how to do so (Copyright Litigation (COPYLITG on Westlaw) is
good enough for that).
I want to know why you guys (Fsf for the GCC plugins, and various kernel
copyright holders for the kernel patch) will not sue GrSecurity, and why
there is no discussion.
You just won't discuss this blatant foundational violation.
Why has my post been spam filtered/black holed.
On 2019-11-01 07:02, Jean Louis wrote:
> * gameonlinux@redchan.it <gameonlinux@redchan.it> [2019-11-01 00:03]:
>> I tried to send this to the list, but it was dropped as spam, which is
>> no
>> surprise since the some want to screen communications to RMS and thus
>> control him.
>
> ... cut...
>
>> Wouldn't the FSF have standing regarding the GCC plugins atleast?
>> Couldn't you all rally linux-kernel copyright holders to bring a joint
>> action?
>>
>> References:
>> perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/
>>
>> perens.com/static/OSS_Spenger_v_Perens/0_2018cv15189/docs1/pdf/18.pdf
>> (Page 10 onward of this brief gives a good recitation of the facts and
>> issues
>
> Recommended reads:
>
> Enforcing the GNU GPL by Eben Moglen
> https://www.gnu.org/philosophy/enforcing-gpl.html
>
> and
>
> The Principles of Community-Oriented GPL Enforcement by Joshua Gay
> https://www.fsf.org/licensing/enforcement-principles
>
> Jean
prev parent reply other threads:[~2019-11-02 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 23:02 gameonlinux
2019-11-01 7:02 ` Jean Louis
2019-11-02 0:48 ` gameonlinux [this message]
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=b07b73864b9e65d220437f38d7ad746e@redchan.it \
--to=gameonlinux@redchan.it \
--cc=ams@gnu.org \
--cc=bruce@perens.com \
--cc=bugs@gnu.support \
--cc=esr@thyrsus.com \
--cc=gnu-system-discuss@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rms@gnu.org \
--cc=torvalds@linux-foundation.org \
/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®