Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58793A24.22555.3425E964@pageexec.freemail.hu>
Date: Fri, 13 Jan 2017 21:35:48 +0100
From: "PaX Team" <pageexec@...email.hu>
To: Kees Cook <keescook@...omium.org>
CC: "AKASHI, Takahiro" <takahiro.akashi@...aro.org>,
        Mark Rutland <mark.rutland@....com>,
        park jinbum <jinb.park7@...il.com>,
        "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: Introduction

On 13 Jan 2017 at 11:06, Kees Cook wrote:

> Out of curiosity, do you remember which bug? I'd be curious to compare
> it against others. It seems like adding structleak to upstream still
> has value, even if the coverage isn't as complete as stackleak.

i think it was CVE-2013-2141 where siginfo has at least one __user ptr field.


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.