oss-security - Re: Re: Problems in automatic crash analysis frameworks

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJ_zFkLBWHz6V9uQPDg50BiXuQBJBLKUB5copEL64fh1C+HBvw@mail.gmail.com>
Date: Thu, 16 Apr 2015 13:49:03 -0700
From: Tavis Ormandy <taviso@...gle.com>
To: Tyler Hicks <tyhicks@...onical.com>
Cc: oss-security@...ts.openwall.com, 
	Assign a CVE Identifier <cve-assign@...re.org>, security <security@...ntu.com>, 
	Stéphane Graber <stgraber@...ntu.com>
Subject: Re: Re: Problems in automatic crash analysis frameworks

On Thu, Apr 16, 2015 at 11:17 AM, Tyler Hicks <tyhicks@...onical.com> wrote:
>
> We've decided to disable support for gathering crash reports of
> containerized processes (see USN-2569-2).
>
> We may reintroduce the feature, with a different implementation, in the
> future. The current idea is described in this feature bug:
>
>   https://launchpad.net/bugs/1445064
>
> Please leave any comments on the proposed design in the feature bug.
>
> Many thanks for thinking through the old implementation and follow up
> patches, Tavis.
>
> Tyler

Thanks Tyler, I guess you don't need me to tell you the new update
looks solid :-)

I'll keep an eye on the new design as it develops.

Tavis.

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.