full-disclosure - Re: what we REALLY learned from WMF

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060106161207.GB6924@dvb>
Date: Fri Jan  6 19:35:38 2006
From: devdas at dvb.homelinux.org (Devdas Bhagat)
Subject: Re: what we REALLY learned from WMF

On 05/01/06 16:07 -0800, Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
<snip>
> 
> If the security issue has been responsible disclosed, there is a process 
> that is needed to build a patch and test the patch.  Some issues take 
> more than 'days' sir.  And testing takes time as well, sir.
> 
A question for people who find such exploitable bugs and report them
upstream. 

How many days does it take for upstream to patch and release bugfix?
It would be nice if you could include the severity of the bug as well.
(Vendor and product names, product versions would be nice as well).
Quite a few of us generally get to know only when the fix is released.

Devdas Bhagat