Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 26 Sep 2014 20:13:15 +0200
From: Peter Bex <>
Subject: Re: Re: CVE-2014-6271: remote code execution through bash (3rd vulnerability)

On Fri, Sep 26, 2014 at 12:07:34PM -0600, Kurt Seifried wrote:
> This is a classic case of "yes the correct thing to do is..." but the
> reality is "we should fix this centrally rather than try to make
> everyone do the right thing (aka boiling the ocean)". This is like tmp
> vulns, it's 2014, the solution for tmp vulns is polyinstantiated /tmp
> per user, and per application /tmp dirs in addition to this. Solve it
> once centrally (e.g. in PAM/systemd) and boom, done.
> We should always try to do the best/safest thing because most devs are
> going to try to do the most insanely dangerous thing.

That's the first sensible thing I've read on this whole topic :)


Powered by blists - more mailing lists

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.