From: Rik van Riel <riel@redhat.com>
To: Brad Spengler <spender@grsecurity.net>,
kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Stop the plagiarism
Date: Sat, 03 Jun 2017 13:32:35 -0400 [thread overview]
Message-ID: <1496511155.29205.109.camel@redhat.com> (raw)
In-Reply-To: <20170603113007.GA1544@grsecurity.net>
On Sat, 2017-06-03 at 07:30 -0400, Brad Spengler wrote:
> While I'm here:
> http://openwall.com/lists/kernel-hardening/2017/06/02/3
>
> "a value linux-hardened and grsecurity have used for a long time now"
> Rik, you're giving credit to a project that didn't even exist a
> couple
> weeks ago, yet they've somehow used it "for a long time", even though
CopperheadOS has been around for a few years now, with
a hardened Linux kernel as one of its components.
> it only exists there because it was copy+pasted from grsecurity? Is
> that what we do now, credit plagiarists instead of the actual authors
> of
> the work? Sorry, but the "work" of struggling to understand code
> that
> isn't yours doesn't suddenly make it your code.
The actual code in my patch is different from the #ifdef
stuff in both linux-hardened and grsecurity.
The only thing that is the same is an integer constant.
> This is exactly how your plagiarism works.
If I wanted to do plagiarism, I would have copied the
ugly-as-all-hell #ifdef magic from grsecurity. What
do you think would have happened if I had submitted
something like this to lkml?
#ifdef CONFIG_PAX_SEGMEXEC
#define ELF_ET_DYN_BASE ((current->mm->pax_flags &
MF_PAX_SEGMEXEC) ? SEGMEXEC_TASK_SIZE/3*2 : TASK_SIZE/3*2)
#else
#define ELF_ET_DYN_BASE (TASK_SIZE / 3 * 2)
#endif
#ifdef CONFIG_PAX_ASLR
#ifdef CONFIG_X86_32
#define PAX_ELF_ET_DYN_BASE 0x10000000UL
#define PAX_DELTA_MMAP_LEN (current->mm->pax_flags &
MF_PAX_SEGMEXEC ? 15 : 16)
#define PAX_DELTA_STACK_LEN (current->mm->pax_flags &
MF_PAX_SEGMEXEC ? 15 : 16)
#else
#define PAX_ELF_ET_DYN_BASE 0x400000UL
#define PAX_DELTA_MMAP_LEN ((test_thread_flag(TIF_ADDR32)) ? 16 :
TASK_SIZE_MAX_SHIFT - PAGE_SHIFT - 3)
#define PAX_DELTA_STACK_LEN ((test_thread_flag(TIF_ADDR32)) ? 16 :
TASK_SIZE_MAX_SHIFT - PAGE_SHIFT - 3)
#endif
#endif
Notice how the code in my patch does not look like that,
at all?
> This is your last warning. This is not a new problem and it needs to
> end completely, or I will make sure it ends.
The grsecurity code you published is licensed under the
GPLv2. I would be happy to add your copyright in if I
ever copied around a larger piece of code, but most of
the time the code I end up submitting is a rewrite and
not a copy.
next prev parent reply other threads:[~2017-06-03 17:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 11:30 [kernel-hardening] Stop the plagiarism Brad Spengler
2017-06-03 13:53 ` Daniel Micay
2017-06-03 14:21 ` Brad Spengler
2017-06-03 15:55 ` Daniel Micay
2017-06-04 3:28 ` Brad Spengler
2017-06-04 14:15 ` Daniel Micay
2017-06-05 0:12 ` Brad Spengler
2017-06-05 1:21 ` Daniel Micay
2017-06-05 1:44 ` Daniel Micay
2017-06-04 12:49 ` Brad Spengler
2017-06-04 13:48 ` Hector Martin
2017-06-04 14:44 ` Brad Spengler
2017-06-04 16:59 ` Hector Martin
2017-06-03 15:08 ` Lionel Debroux
2017-06-03 15:16 ` Matt Brown
2017-06-03 17:32 ` Rik van Riel [this message]
2017-06-04 7:16 ` Kees Cook
2017-06-04 11:43 ` Brad Spengler
2017-06-06 0:29 ` Kees Cook
2017-06-06 13:05 ` [kernel-hardening] " Jonathan Corbet
2017-06-05 17:43 ` [kernel-hardening] " Pavel Labushev
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=1496511155.29205.109.camel@redhat.com \
--to=riel@redhat.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=spender@grsecurity.net \
/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).