full-disclosure - Re: Mr. Magorium's Wunderbar Emporium

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 for Android: free password hash cracker in your pocket

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

Date: Sun, 16 Aug 2009 02:43:10 -0400
From: Valdis.Kletnieks@...edu
To: security curmudgeon <jericho@...rition.org>
Cc: full-disclosure@...ts.grok.org.uk, dailydave@...ts.immunitysec.com
Subject: Re: Mr. Magorium's Wunderbar Emporium

On Sat, 15 Aug 2009 07:07:53 -0000, security curmudgeon said:
> On Fri, 14 Aug 2009, Valdis.Kletnieks@...edu wrote:
> : Of course, getting a CVE for that issue would have forced disclosure of 
> : the bug too, quite possibly before the vendors were ready to ship 
> 
> Huh? Apparently you don't know how CVE assignment works.
> 
> If you request one from CVE, they can assign one without knowing any 
> details of the vulnerability. CVE will embargo the details until the 
> researcher and/or vendor are ready. I assume the Candidate Numbering 
> Authorities would be able to do the same, but going to Red Hat, Debian or 
> Ubuntu in this case may not be the best option.

Yes, but to make the CVE actually *useful*, they need to eventually release
it.  Sure, I may have 5 or 10 CAN in my pocket - and I can even wave around
CAN-2009-3439 and say 'Death of Internet Predicted'.  But for the CAN/CVE
to be *useful*, it needs to be disclosed.

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/