From: gameonlinux@redchan.it
To: linux-kernel@vger.kernel.org
Subject: Why isn't Grsecurity being sued for its long standing GPL violations??
Date: Mon, 09 Sep 2019 21:23:22 +0000 [thread overview]
Message-ID: <f009c26462922b125d65a21041e22f12@redchan.it> (raw)
Hi, RMS and Bruce Perens;
I noticed that recently Grsecurity's Brad Spengler (who sued you, Bruce,
for speaking the truth), decided to "Flex" and basically advertise while
chastising the linux community:
news.ycombinator.com/item?id=20874470
Another poster then pointed out the history of Grsecurity's copyright
violations (as a derivative work that is restricting redistribution),
but said he didn't want to say to much, because he didn't want to get
sued. He referenced your good write-up on the situation:
perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/
(Which has not changed)
Why isn't Grsecurity being sued for it's copyright violations? They've
been going on for years now. Clearly their scheme works: it can be shown
to a court both the attempt to restrict redistribution was tendered (the
agreement) and that said attempt has been successful.
Also isn't Open Source Security simply an alter-ego of Brad Spengler?
Him being the only employee? Couldn't the corporate veil be pierced and
he be found personally liable for any damages?
next reply other threads:[~2019-09-09 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 21:23 gameonlinux [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-15 19:17 Why isn't Grsecurity being sued for its long standing GPL violations? gameonlinux
2019-09-15 4:36 Why isn't Grsecurity being sued for its long standing GPL violations?? gameonlinux
2019-09-09 4:47 Why isn't Grsecurity being sued for its long standing GPL violations? gameonlinux
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=f009c26462922b125d65a21041e22f12@redchan.it \
--to=gameonlinux@redchan.it \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).