Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 18 Dec 2014 10:52:38 +0100
From: Florian Weimer <>
Subject: Embargoes for secondary issues

Suppose we have an unfixed, public issue, and while working on a fix, 
other issues in the same code are discovered which are different flaws, 
but have similar impact than the original issue.

Do we need an embargo for the secondary issues, or can we just make them 
public immediately?  I would strongly prefer the latter.

Florian Weimer / Red Hat Product Security

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.