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

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

Message-ID: <20021006153404.F28295-100000@birmingham-infragard.org>
From: daniel_clemens at birmingham-infragard.org (daniel.clemens)
Subject: zen-parse@....de is not zen-parse@....net

> 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*?


I think what the apache developers might be saying may sound something
closer to ' I/We think that this type of disclosure is more realistic' (

Assuming that their was a blackhat that developed the hack and it had been
0day for a while with that particular blackhat/or blackhatters....)

-Dan

> --
> Florian Weimer 	                  Weimer@...T.Uni-Stuttgart.DE
> University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
> RUS-CERT                          fax +49-711-685-5898
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>

------------------------------------
http://www.birmingham-infragard.org
                   p.  205.328.4200
               emerg.  877.806.8928

Esse quam videra
    (to be, rather than to appear)
-----------------------------------