From 18459c67b07e68b67d77887d0d9e4bcc97d20ad8 Mon Sep 17 00:00:00 2001 From: Marco Squarcina Date: Mon, 21 Oct 2019 12:28:32 +0200 Subject: [PATCH] added info on how to submit ctf writeups --- README.md | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 33bd223..b6b1947 100644 --- a/README.md +++ b/README.md @@ -15,9 +15,9 @@ The course is coordinated by: * Mauro Tempesta aka `MrStorm`, [twitter](https://twitter.com/mau_tempesta) * Michael Pucher aka `cluosh` -Communication and announcements on [mattermost](https://mattermost.w0y.at). +Communication and announcements on [mattermost](https://mattermost.w0y.at), please refer to this [guide](mattermost_for_CTFs.md) on how to use use Gitlab/Mattermost for collaboration during CTFs. -Send questions to [ctf@secpriv.tuwien.ac.at](mailto:ctf@secpriv.tuwien.ac.at). +Send your questions - if any - to [ctf@secpriv.tuwien.ac.at](mailto:ctf@secpriv.tuwien.ac.at). Meetings @@ -35,3 +35,18 @@ Tentative Schedule * 10/12, TBA, TBA, Talks * 17/12, 17:00 - 20:00, FAV Hörsaal 1, Talks + +CTF Participation +----------------- +As specified in the [Course intro](meetings/20191015/course-intro.pdf), each student is required to attend at least 1 CTF on-site and 3 CTFs overall. On-line attendance is assessed via an individual detailed write-up reporting everything that has been done during the competition, including failed attempts at solving challenges. No write-up is required to prove on-site attendance. + +Write-ups must be submitted directly on [Gitlab](https://gitlab.w0y.at/ctf-seminar/ws19) under the directory `writeups//` as a single Markdown file called after the CTF. Say, for instance, that your handle is `l33th4ck3r` and you want to submit the write-up for the SECCON'19 CTF, then just create the file `writeups/l33th4ck3r/seccon19.md`. If you need to store additional files to complement your write-up, such as scripts or screenshots, add a subfolder (such as `writeups/l33th4ck3r/seccon19/`) in your own directory and save those files there. + +Your write-up file should provide an overall personal consideration of the CTF in retrospective and then a detailed technical analysis of the challenges that you attempted to solve, either successfully or not. + +Please submit your write-up within 2 weeks after the end of the CTF. + + +Talks +----- +TBA \ No newline at end of file -- 2.43.0