full-disclosure - DJB's contest (repost after being moderated on BGTQ)

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

Message-ID: <009301c4ea9f$2e56b2f0$2080fea9@p14n>
From: support at sabre-security.com (support@...re-security.com)
Subject: DJB's contest (repost after being moderated on
	BGTQ)

Hey all, DJB,

>> Is the class on responsible disclosure next semester perhaps?

Responsible disclosure is a euphemism creating by industry lobby groups
like OIS, which never had much support in the security scene in the first 
place.

> The reason that the 16 students sent their 91 reports to me privately is
> so that they wouldn't have to deal with people like you. It was entirely
> my decision to send out these 44 public notices.

If I am allowed to suggest something for a possible re-run of the same 
course:
It would probably be more interesting to set a lower bar on the number of
vulnerabilities but to restrict the focus a bit more -- e.g. asking for 1 
remotely
exploitable bug in a list of widely used software (Bind/OpenSSH/ProFTPd (or 
even QMail :-)
would focus students on larger pieces of software that are a bit more 
critical than
e.g. nasm. This would lead to the students searching for less "standardized" 
problems,
as well.

Then again, it sounds like a really fun course :)

Cheers,
Thomas Dullien 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20041225/1ebad459/attachment.html