full-disclosure - zen-parse@....de is not zen-parse@....net

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]

From: Weimer at CERT.Uni-Stuttgart.DE (Florian Weimer)
Subject: zen-parse@....de is not zen-parse@....net

zen-parse <zen-parse@....net> writes:

> With regards to dealing with iDefense: It's an easier way for me to make
> sure something is disclosed in an appropriate manner than me finding and
> contacting all the people who need to be myself. And it gives me some
> money, which, believe it or not, is useful to have occasionally. 

IMHO, the iDefense approach is highly questionable.  But I won't argue
with you in particular about it.

However, it's highly surprising that the Apache developers call the
iDefense approach "reasonable disclosure".  Is it reasonable to
disclose critical information on new security vulnerabilities to
potential but paying blackhats *on* *the* *same* *day* *the* *vendors*
*are* *notified*?

-- 
Florian Weimer 	                  Weimer@...T.Uni-Stuttgart.DE
University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT                          fax +49-711-685-5898