From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Cc: nisus@redchan.it
Subject: Re: [kernel-hardening] Yes you have standing to sue GRSecurity.
Date: Sat, 29 Jul 2017 15:38:44 +0200 [thread overview]
Message-ID: <20170729133844.GA5033@openwall.com> (raw)
In-Reply-To: <50c85baff48b33095955d3bbce6004cc@redchan.it>
Hi all,
As a moderator, I reluctantly accepted this message on kernel-hardening,
and rejected its copy sent a bit later to oss-security - it's more than
enough to have this on one of these two lists.
No followups to it, please. Let's focus on actual kernel hardening, not
on the drama.
As a person, I strongly oppose legal threats in our community. Both
grsecurity's and those against them. Please don't. Regardless of who's
right or wrong, let alone who's side the law might be on (which I guess
different attorneys wouldn't easily agree on). When you resort to legal
threats, you're wrong.
Alexander
next prev parent reply other threads:[~2017-07-29 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 12:40 [kernel-hardening] Yes you have standing to sue GRSecurity nisus
2017-07-29 13:38 ` Solar Designer [this message]
2017-07-30 19:54 ` Solar Designer
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=20170729133844.GA5033@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=nisus@redchan.it \
/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.