Date: Fri, 26 Jan 2018 20:34:48 +0100 From: Solar Designer <solar@...nwall.com> To: oss-security@...ts.openwall.com Subject: Re: How to deal with reporters who don't want their bugs fixed? On Sat, Jan 20, 2018 at 09:18:25PM +0100, Florian Weimer wrote: > On 01/18/2018 10:21 PM, Solar Designer wrote: > >I think it's best for your project (I guess glibc?) to prominently > >publish near the security contact address a maximum embargo time you'd > >(be likely to) agree to. That's what security at kernel.org does > >(7 days) and what we do with (linux-)distros (14 days). > > I would prefer to be flexible in case something truly awful happens. As an option, you may state that your project will agree to embargoes of up to e.g. 14 days (as long as there's no leak, etc.), but at your sole discretion might agree to longer embargoes (ditto). > Your perspective is skewed because people know that you have a > preference for short embargoes, so at least I tell people to make sure > that they have a final patch before contacting the distros list. Then a > week or two is probably enough in most cases. Without a patch, not so much. As another option, you can state a longer maximum embargo for your project - e.g., 30 days - although that seems excessive to me. I understand that for complex or/and complicated issues it might take a lot of time to come up with what looks like a final fix, but as you point out below it might also be unrealistic to expect that fix to actually be final. So maybe it's best not to even try, and instead to release non-invasive preliminary mitigations first (clearly calling them such), then work on cleaner and more complete fixes in public. > On the other hand, it is near impossible to develop quality solutions > under long embargoes. We tried that in 2008 and largely failed. > >That way, it's > >less important for you to judge whether the reason for embargo is > >valid/altruistic or bogus/selfish - a sane maximum embargo time > >minimizes the damage to all parties either way. > > That's not really true. Depending on the nature of the vulnerability, > there can be a lot of work before we're confident that we can ship an > update. We have some rather bad code out there, with very little or no > test coverage, and if we modify such code, we really need to make sure > that users receive a net improvement. (For example, we thought we had > the final patch for a DNS stub resolver issue, but it turned out very > late that it had a crippling memory leak.) I think we're on the same page here. This is a reason to avoid long embargoes, and in complex/complicated cases to avoid even trying to make the very first public updates "final". Alexander
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.