• Don't be a dick
• No automated scanners, especially against as we do have resource constraints. TCTF is very sensitive politically so if we get even one person running a bunch of scans we can get taken offline. We can also can work with ITSO to see which GMU student did it pretty easily, so don't risk it.
• Do not run exploits against the CTF platform. Only run exploits against the C exploitation ports (not 443 or 80). These ports are explicitly handed to you and don't need scans.
• Should you find an exploit or an unintended benefit, please report it to [email protected]
• Be wary of other IPs given on this platform and tread lightly with them. The CC exec members aren't the only challenge writers, and we can't speak for how those servers are operated.

If you have rules questions, email [email protected] or ask in Slack. Only Exec board members and Challenge authors should help in public chats, but feel free to DM each other to cooperate on problems. This is a TRAINING ctf, so there's no prize for getting first (other than that sweet, sweet scoreboard screenshot at the end of the semester).