Code Monkey home page Code Monkey logo

write-ups-2016's Introduction

CTF write-ups 2016

Gitter Reddit Twitter Follow

External Coverage Internal Coverage

There are some problems with CTF write-ups in general:

  • They’re scattered across the interwebs
  • They don’t usually include the original files needed to solve the challenge
  • Some of them are incomplete or skip ‘obvious’ parts of the explanation, and are therefore not as helpful for newcomers
  • Often they disappear when the owner forgets to renew their domain or shuts down their blog

This repository aims to solve those problems.

It’s a collection of CTF source files and write-ups that anyone can contribute to. Did you just publish a CTF write-up? Let us know, and we’ll add a link to your post — or just add the link yourself and submit a pull request. Spot an issue with a solution? Correct it, and send a pull request.

Contributing

Please read CONTRIBUTING.md.

Archive

write-ups-2016's People

Contributors

0xf4b avatar adriaandens avatar akrasuski1 avatar arthaud avatar bcyrill avatar boaster avatar dhanvi avatar doyler avatar elliptic-shiho avatar glen-mac avatar hellman avatar jermenkoo avatar kablaa avatar kajer avatar laxa avatar lionaneesh avatar liveoverflow avatar m1ghtym0 avatar nopresearcher avatar oalieno avatar owlz avatar p1kachu avatar parthkolekar avatar qcgvkzeg avatar stefan2904 avatar thotypous avatar tothi avatar unicornsasfuel avatar vvvverre avatar x0w1 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

write-ups-2016's Issues

Splitting up CTFs to make the repo more acccessbile

I think using a single branch per ctf might be a good way to go about it. For 2016, you can make an empty branch now then the process is:

  1. git clone -b empty_ctf --single-branch [url] (or git checkout empty_ctf if you are the maintainer of the master)
  2. git checkout -b [ctf_name]

or if the branch already exists for that ctf:

  1. git clone -b [ctf_name] --single-branch [url]

Then once this branch exists the maintainer of the master just needs to:

  1. git checkout master
  2. git merge [ctf_name]

A single branch per ctf allows people to work on the repository without having to clone the entire master branch as it gets bigger. Github also allows users to download a zip of specific branches from the website which is very nice if people want to download a particular ctf and play with those challenges.

I was messing around with the idea here: https://github.com/cm-recruit/write-ups-2016/tree/master

Nullcon HackIm

https://ctftime.org/event/285

I was able to download public files for several challenges.

However, some challenges require to solve previous challenges - and I got no time for that.

So here is a list of challenges that somebody else has to download or get a hold of:

  • crypto/crypto-200
  • crypto/crypto-500-2
  • programming/programming-400
  • programming/programming-500
  • re/prisonbreak
  • exploitation/exploitation-4
  • misc/lol-400
  • forensics/file-and-folders-500
  • trivia/trivia-400
  • web/HQLoL-500

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.