From: Greg KH <gregkh@linuxfoundation.org>
To: aconcernedfossdev@airmail.cc
Cc: ubuntu-users@lists.ubuntu.com,
ubuntu-devel-discuss@lists.ubuntu.com,
kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Why does no one care that Brad Spengler of GRSecurity is blatantly violating the intention of the rightsholders to the Linux Kernel?
Date: Thu, 15 Jun 2017 17:43:34 +0200 [thread overview]
Message-ID: <20170615154334.GA786@kroah.com> (raw)
In-Reply-To: <f335eb911db2e2d2867a31722dd45769@airmail.cc>
On Thu, Jun 15, 2017 at 03:34:06PM +0000, aconcernedfossdev@airmail.cc wrote:
> Why does no one care that Brad Spengler of GRSecurity is blatantly violating
> the intention of the rightsholders to the Linux Kernel?
> He is also violating the license grant, Courts would not be fooled by his
> scheme to prevent redistribution.
>
> The license grant the Linux Kernel is distributed under disallows the
> imposition of additional terms. The making of an understanding that the
> derivative work must not be redistributed (lest there be retaliation) is the
> imposition of an additional term. The communication of this threat is the
> moment that GRSecurity violates the license grant. Thence-forth
> modification, making of derivative works, and distribution of such is a
> violation of the Copyright statute. The concoction of the transparent scheme
> shows that it is a willful violation, one taken in full knowledge by
> GRSecurity of the intention of the original grantor.
If you feel that what they are doing is somehow violating your copyright
on the Linux kernel, then you have the right to take legal action if you
so desire. To tell others what to do, however, is not something that
usually gets you very far in the world.
Best of luck!
greg k-h
next prev parent reply other threads:[~2017-06-15 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 15:34 [kernel-hardening] Why does no one care that Brad Spengler of GRSecurity is blatantly violating the intention of the rightsholders to the Linux Kernel? aconcernedfossdev
2017-06-15 15:43 ` Greg KH [this message]
2017-06-15 15:51 ` aconcernedfossdev
2017-06-15 15:56 ` aconcernedfossdev
2017-06-15 15:58 ` W Stacy Lockwood
2017-06-15 16:05 ` J
2017-06-15 16:17 ` aconcernedfossdev
2017-06-15 16:21 ` aconcernedfossdev
[not found] ` <20170615182504.640de5f0@utnubu>
[not found] ` <e74023b9943f2341bd84f2f274b8dab2@airmail.cc>
2017-06-15 16:33 ` aconcernedfossdev
2017-06-15 15:53 ` [kernel-hardening] " Casey Schaufler
2017-06-15 16:01 ` aconcernedfossdev
2017-06-15 16:05 ` Wade Smart
2017-06-15 16:27 ` aconcernedfossdev
2017-06-15 15:58 ` Rik van Riel
2017-06-15 16:05 ` aconcernedfossdev
[not found] ` <1497548717.20270.95.camel@redhat.com>
[not found] ` <a2a6719beae85e1835e8a71c1839c3d4@airmail.cc>
2017-06-15 19:25 ` aconcernedfossdev
2017-06-15 17:26 ` Solar Designer
[not found] ` <0cf439c8a01b4f66bcc4bf26d70f47cf@xenhideout.nl>
[not found] ` <7d00d451d9a9abfb79eef0b38921262b@airmail.cc>
[not found] ` <38a2911da98c0c05aa7912455b668288@jots.org>
2017-06-15 19:37 ` Idle curiosity aconcernedfossdev
[not found] ` <CAOdo=Swu_Uz7MH0NNAeO+7m=wZqG1EgHwKA8B0CgQUuxNefLvg@mail.gmail.com>
[not found] ` <954efb3ca8d72bc8b3f229bca316354f@airmail.cc>
[not found] ` <CAAiDhw1ZqR_ncw7y1UJH=PjRNK6rw6GitNTsSTeontEQ4M8mzg@mail.gmail.com>
[not found] ` <5690.5942c0fe.5f6d7@roo.daria.co.uk>
[not found] ` <CAAiDhw3k821f1-S=W9yrQM1CjPvORmMB2+OYzuifVfWT4e8oYQ@mail.gmail.com>
[not found] ` <800f1b05d29f3423df5cd39cf2995a42@airmail.cc>
[not found] ` <CAAiDhw3c4EbnWFaXS+KSNrrVoF3uh7jQGZj+_UEurrOxc9Y_NA@mail.gmail.com>
[not found] ` <757b458494b8727a5bf8fe51f0d2d84f@airmail.cc>
2017-06-15 19:47 ` Fwd: Re: Why does no one care that Brad Spengler of GRSecurity is blatantly violating the intention of the rightsholders to the Linux Kernel? aconcernedfossdev
[not found] ` <CAAiDhw3E_bDxGcK_fHJ1xQvA0F3sN9H+Je+x+27w5ueLrwVkfA@mail.gmail.com>
2017-06-15 19:53 ` aconcernedfossdev
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=20170615154334.GA786@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aconcernedfossdev@airmail.cc \
--cc=kernel-hardening@lists.openwall.com \
--cc=ubuntu-devel-discuss@lists.ubuntu.com \
--cc=ubuntu-users@lists.ubuntu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.