full-disclosure - How much time is appropriate for fixing a bug?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120704204918.GJ27473@Jann-PC.fritz.box>
Date: Wed, 4 Jul 2012 22:49:18 +0200
From: Jann Horn <jannhorn@...glemail.com>
To: full-disclosure@...ts.grok.org.uk
Subject: How much time is appropriate for fixing a bug?

After having reported a security-relevant bug about a smartphone, how long would
you wait for the vendor to fix it? What are typical times?

I remember telling someone about a security-relevant bug in his library some time
ago - he fixed it and published the fixed version within ten minutes. On the
other hand, I often see mails on bugtraq or so in which the given dates show that
the vendor took maybe a year or so to fix the issue...

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/