[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1496627055.21652.4.camel@gmail.com>
Date: Sun, 04 Jun 2017 21:44:15 -0400
From: Daniel Micay <danielmicay@...il.com>
To: Brad Spengler <spender@...ecurity.net>
Cc: kernel-hardening@...ts.openwall.com, pageexec@...email.hu
Subject: Re: Stop the plagiarism
> migrating it to get_random_long to the write people with a
s/write/right/
Which is why Jann's submission of a patch earlier didn't land despite it
being really clearly cut, and I really have no idea about any previous
attempts. I have no interest in researching any previous attempts to get
it fixed and guessing at why those never landed. You care who found and
fixed it first, I didn't, so I didn't look into it. That doesn't mean I
wanted credit for fixing it. I would have been happier if Jann, Kees or
Riel had submitted it instead since it's less to deal with.
It needed to be fixed before masking out one of the bytes so I made yet
another fix for it and submitted it.
When you showed up on IRC mad at me, I thought it was about the
__ro_after_init changes which referenced PaX so I couldn't understand
what you were talking about because *I didn't take this change from PaX
like those ones*. Apparently quite hard to understand.
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.
