From: linuxgpletc@redchan.it
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Ivan Ivanov <qmastery16@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
gentoo-user@lists.gentoo.org, freebsd-chat@freebsd.org,
misc@openbsd.org, rms@gnu.org
Subject: Re: GRSec is vital to Linux security
Date: Thu, 24 Jan 2019 16:22:00 +0000 [thread overview]
Message-ID: <a4ae3c98c10eeac39c404b60a0e4d538@redchan.it> (raw)
In-Reply-To: <3efc6268-747d-0841-4249-5804fa9095ca@metux.net>
On 2019-01-24 15:31, Enrico Weigelt, metux IT consult wrote:
> Do you have some actual proposals / patches ?
Sue Open Source Security / Bradly Spengler for copyright infringement.
Seek his profits as damages. I doubt you'll be able to get specific
performance since the GPL is not a contact in this instance. (If you
registered your copyright prior to the violation you can alternatively
go for statutory damages + attoneys fees btw)
He is _blatantly_ violating your copyright by adding an additional
restrictive term regarding the distribution of his non-separable
derivative work of the linux kernel code.
next prev parent reply other threads:[~2019-01-24 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 18:19 linuxgpletc
2019-01-23 20:46 ` Ivan Ivanov
2019-01-23 22:28 ` linuxgpletc
2019-01-24 15:31 ` Enrico Weigelt, metux IT consult
2019-01-24 16:03 ` Adam Borowski
2019-01-24 16:22 ` linuxgpletc [this message]
2019-01-24 16:31 ` GRSec is vital to Linux security -- SFConservancy = legal malpractice. Use own lawyer linuxgpletc
2019-01-24 16:40 ` Fwd: Re: GRSec is vital to Linux security linuxgpletc
2019-01-28 20:20 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission linuxgpletc
2019-01-29 8:51 ` linuxgpletc
2019-01-29 9:10 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update) linuxgpletc
2019-01-29 9:38 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update 3) linuxgpletc
2019-01-24 16:53 GRSec is vital to Linux security linuxgpletc
2019-01-24 20:18 ` Boris Lukashev
2019-01-25 16:34 ` linuxgpletc
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=a4ae3c98c10eeac39c404b60a0e4d538@redchan.it \
--to=linuxgpletc@redchan.it \
--cc=freebsd-chat@freebsd.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=misc@openbsd.org \
--cc=qmastery16@gmail.com \
--cc=rms@gnu.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
Powered by JetHome