[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPshzHbwitYkpBXf4e3jbR7SXKCvPgw8R+UbWHSQRaK0vMshVg@mail.gmail.com>
Date: Fri, 12 May 2017 13:34:29 +0200
From: Hunger <hunger@...ger.hu>
To: Kees Cook <keescook@...omium.org>
Cc: PaX Team <pageexec@...email.hu>, Mathias Krause <minipli@...glemail.com>,
Daniel Cegielka <daniel.cegielka@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: It looks like there will be no more public
versions of PaX and Grsec.
On Thu, May 11, 2017 at 8:02 PM, Kees Cook <keescook@...omium.org> wrote:
> Your work has made
> the world a little more secure. I'm doing my best to make the world a
> lot more secure
PaX and grsecurity had an influence on the whole industry. Every modern OS
have NX support and ASLR now from Apple to Microsoft. PIE binaries and
mprotect restrictions in Apple iOS. PaX UDEREF and KERNEXEC features
implemented in hardware level, like ARM PXN, PAN and Intel SMEP, SMAP
(still weaker protection than PaX btw). PaX RAP is leading in Control Flow
Integrity.
So how you make the world a lot more secure while just copy+pasting the 10+
years old grsecurity and PaX features and innovating nothing new?
> If a financial arrangement is desired, I believe
> my employer continues to be willing to explore it now just as they
> have in the past.
>
If i read it correctly, pipacs and spender got no financial arrangement or
any contact attempt about it in the past, so what will your employer
continue?
Content of type "text/html" skipped
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.
