search

ctfs / resources

A general collection of information, tools, and tips regarding CTFs and similar security competitions
ctfs.github.io/resources
Creative Commons Zero v1.0 Universal
1.75k stars 279 forks source link

Draft first, write later? #1

Closed dufferzafar closed 10 years ago

dufferzafar commented 10 years ago

It'd be nice knowing the topics before hand. For eg, you just wrote about crypto/md5, Do you plan to write about other hashing schemes as well (SHA, RIPEMD). In case you do, just create folders with empty README files in them.

This would help people like me, who can contribute but are not sure of the topic that should be written next.

Thanks for doing this, I hope this serves as a definitive guide to CTFs.

cabreraalex commented 10 years ago

I'll try to add as many topics as I can and know about! Would a blank README with a simple header be enough? I'm going to update the contributing guide and add an EXAMPLE.md to make the contributions standardized. Thank you for showing interest!

Also, since the topics are very broad and encompass many technologies, I'm hoping people will be able to simply add a folder and README for any topics missing. Eventually we might have to start sub-categorizing too.

dufferzafar commented 10 years ago

Yes, a blank README with just a header shall suffice.

And as CTFs can be about almost anything under the technology sun, we have a lot of writing to do.

I think a better approach would be to first create a bullet list of the stuff we are going to write, and then move on with a milestone based approach.

We could first write about the most basic stuff and so on. Would love to hear your thoughts...

cabreraalex commented 10 years ago

Yeah, that's actually sort of what I was thinking. Since CTF topics are tremendously large, we might have to start sub-categorizing to keep order, but for now we can keep it broadly organized. I set a milestone to complete the top-level README's which will provide the base for the other topics.

Since it will be impossible to write everything about CTFs in one go, I think the best approach is to focus on basic principles as if it were your first time seeing a CTF.

For example, we can start Web off with an introduction to HTTP and simple header exploits, moving on to packet sniffing with Wireshark and then on to the programming languages (javascript, SQL, PHP). Very simple introductions can be presented in the top-level README, web/README.md, and from there link to the specific topics.

For Crypto I sort of started it off focusing on simple introductory ciphers like the caesar cipher, and from there we can add on with the more modern cryptography techniques like RSA.

I see the top-level READMEs as the basis for organization and introduction, and so I think it would be best to focus on polishing those as good introductory reading material. From there we can link the specific topics and begin adding the core content.

Hope that makes sense, and please suggest anything you feel would make it better!

dufferzafar commented 10 years ago

Okay now that you have created a milestone. We can get down to some real work.

I am not good with the web tools you have mentioned but I can write about Crypto and Stego, only if you don't have a problem with that. Also, I just saw this today: https://github.com/crypto101/book.

cabreraalex commented 10 years ago

Perfect! Yeah, I'm not an expert in any of the fields so I'm just going to work on as much as I can and then hopefully we can gain traction and have more knowledgeable people contribute to their respective focuses.

Eventually I want to maybe transfer ownership to the ctfs group, but I don't think the owner wants to while the repo is so small.

I'll merge your pull requests as I get them and work on it as much as I can.

Thanks!