| 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
| ||
|
Date: Fri, 06 Jul 2012 12:35:27 +0200
From: Philipp Hagemeister <phihag@...hag.de>
To: Jann Horn <jannhorn@...glemail.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: How much time is appropriate for fixing a bug?
Realistically, it will take at least a month to go from security to
development through QA and release (in your case probably twice, because
it may have to go through the carrier's QA/release). Wikipedia says 5
months: http://en.wikipedia.org/wiki/Responsible_disclosure
- Philipp
On 07/04/2012 10:49 PM, Jann Horn wrote:
> 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...
>
>
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists