bugtraq - Digital Armaments May-June-2007 Hacking Challenge: VMware

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: <20070509162157.18192.qmail@securityfocus.com>
Date: 9 May 2007 16:21:57 -0000
From: info@...italarmaments.com
To: bugtraq@...urityfocus.com
Subject: Digital Armaments May-June-2007 Hacking Challenge: VMware

Digital Armaments May-June Hacking Challenge: VMware

Challenge Publication is 09.05.2007
http://www.digitalarmaments.com/challanges_open.html

I. Details

Digital Armaments officially announce the launch of May-June hacking challenge. 

The challenge starts on May 1. For the May-June Challenge, Digital Armaments will give 5000 credits EXTRA plus 2500$ EXTRA for each submission that results in a VMware High Risk Vulnerability. This should include example and documentation. 

The submission must be sent during the May/June months and be received by midnight EST on June 30, 2007. The 5000 credits plus the 2500$ will be an extra added to the normal vulnerability payment (check the DACP scheme).

II. References 

For further information on Digital Armaments Contributor Program (DACP) please refer at:

http://www.digitalarmaments.com/contribute.html

Details of credits value can be found at:

http://www.digitalarmaments.com/contribute.html#credit

III. Legal Notices

Copyright © 2007 Digital Armaments Inc. 

Redistribution of this alert electronically is allowed. It should not be edited in any way. Reprint the whole is allowed, partial reprint is not permitted. For any other request please email customerservice@...italarmaments.com for permission. 

Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.