After a successful event in 2013 we are trying to organize a second CTF/Hacker Scavenger Hunt for BSides Boston 2014. This is a call for challenge submissions. I am looking for interesting infosec focused challenges in the following categories:
Binary / Malware / Shellcode reversing, analysis etc
System or Network Forensics
Infrastructure Security / Configuration
Mobile systems and devices
Whatever other fun ideas or challenges you may have in categories I haven’t dreamed of
The goal is to get a number of challenges representing different disciplines and skill levels. “Entry Level” to “Insanely Difficult” are all encouraged. Special focus and consideration should be given to challenges that can be completed while attending the rest of the conference.
I will be providing a fairly robust infrastructure for hosting software/system/network/binary etc related challenges (technical details will be made available to challenge submitters), a wired and wireless network, and scoring. Participation will be open to challenge submitters (you get a freebie for contributing, although you do actually have to solve it, and you get to make it hard on the competition!!! There will be a rule change on this item this year as suggested. The rule is another team/participant must solve your challenge as well before you can claim points for it).
So who can build the best puzzles and solve the most? Submissions of proposals are due by noon EST April 1 and final submission of challenge materials for QA testing will be due a few weeks before the conf. You’ll likely get an answer pretty quickly so submit early and often. Please consider legal, ethical etc. implications of the challenge. Those who submit, are accepted and fail to deliver will be worth points to competitors :). If you want to help out in ways other than challenge development, let me know.
Name/Contact info (how or if you want to be listed in the credits):
Challenge Description (what will competitors see and do, walk through):
Goal and skills involved:
1-10 Difficulty rating (1 being “good intro to the topic” – 10 “insanely difficult for a pro”):
Special technology or physical requirements:
Has this challenge been used before? Where When? (this is ok, think about what could be changed slightly):
What could go wrong?:
Confirmation you will be available to help fix it if it breaks: