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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri Oct  7 06:57:09 2005
From: offtopic at (offtopic)
Subject: Websites vulnerabilities disclosure

> i recommend you don't use coordinators - they are f*ck*d parasites.

But it take much less effort for researcher - just to send report to any coordinator (freeware like CERT or commercial like iDefense), and forget.
It works in case with software vulnerability but don't works if vulnerability is in public service.
Vulnerability disclosure policies are about "systems" and "services". According to my English - about web applications and other public internet services too. Or not?

PS. About "ethic". Just example - what should to do good-boy CISSP who found vulnerabilities in isc2 if any communication fail :-))?

PPS. About full-disclosure. zone-h is full-disclosure too :-).

(c)oded by

Powered by blists - more mailing lists