[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB-iPKXCPY0-M2EL9GaD670+2UnvTEhk1Tdxasn=Ac6t0JBBAA@mail.gmail.com>
Date: Fri, 6 May 2016 14:58:57 -0700
From: "Leibowitz, Michael" <michael.leibowitz@...el.com>
To: Brad Spengler <spender@...ecurity.net>
Cc: kernel-hardening@...ts.openwall.com, Kees Cook <keescook@...omium.org>,
re.emese@...il.com, pageexec@...email.hu
Subject: Re: [RFC 1/3] Add struct randomizing plugin
On Thu, May 5, 2016 at 2:00 PM, Brad Spengler <spender@...ecurity.net> wrote:
> Hi Michael,
>
>> + * Copyright (c) 2016, Intel Corporation.
>
> Can you please describe exactly what changes of yours to my work justify claiming
> Intel's copyright over even a sliver of the file? What new expression of creativity
> has Intel provided here?
>
> Was it the whitespace changes? The conversion of // to /* */ ? The single typo fix?
> Removing the single line that breaks the plugin when used with the constify plugin?
>
> -Brad
The Intel copyright was applied as it is standard operating procedure.
After some internal discussions, we basically agree. The changes
created here are trivial from the original and the result nearly 100%
your work. The next RFC and any subsequent submissions will not have
the Intel copyright for trivial changes rotely applied.
Regarding the constify plugin breakage, as we don't presently have a
constify plugin, I removed it.
Cheers
--
Michael Leibowitz
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
