From: nipponmail@firemail.cc
To: linux-kernel@vger.kernel.org
Subject: Re: Linksys WRT54G and the GPL - What about GRSECURITY?
Date: Sun, 17 Jan 2021 17:54:25 +0000 [thread overview]
Message-ID: <5d2cbf338414bf0c5bb7ab6f2e85cbf9@firemail.cc> (raw)
Linus etc do not give a FUCK that Grsecurity is BLATANTLY violating the
GPL. So why do you fucking retards complain about this?
> DURR BECUAUSE WE DON'T HAVE 2 DO ANYTHING, CAN JUST COMMISERATE
(
https://perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/
)
next reply other threads:[~2021-01-17 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 17:54 nipponmail [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-17 18:02 Linksys WRT54G and the GPL - What about GRSECURITY? nipponmail
[not found] ` <CAFUG7Cd8S+sGRkKB3z1PoPz14ReaNN=unE6E7tTuFYGB8LqdBA@mail.gmail.com>
2021-01-18 16:05 ` nipponmail
2021-01-18 23:01 ` nipponmail
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=5d2cbf338414bf0c5bb7ab6f2e85cbf9@firemail.cc \
--to=nipponmail@firemail.cc \
--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 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.