Mathias Bynens

If you know of a way to change the regular expression to not have catastrophic backtracking, we'd certainly accept a patch. But note that **this is not a security vulnerability...

https://github.com/ctfs/write-ups-2014 https://github.com/ctfs/write-ups-2015

https://github.com/blog/1986-announcing-git-large-file-storage-lfs would elegantly solve this problem without having to rely on a third-party host. The bad news: > Every user and organization on GitHub.com with Git LFS enabled will begin...

> Most of our contributions come from web-based edits. @captn3m0 Yes, but **_no**_ contributions that actually add challenge files (i.e. tarballs etc.) are web-based edits. (At least, I haven’t seen...

For each pack of 50 GB of storage + 50 GB of bandwidth per month, it’s $5/month. https://github.com/pricing#add-ons

The raw (non-git-lfs) Git repo size would be significantly smaller, though, and `git-lfs` would enable us to host the larger files as closely to the repo as possible (instead of...

Who is going to maintain it?

I agree; sadly it’s not very realistic. People can always `grep` the repository’s contents for the category they’re interested in. This is good enough for me.

“WEB” 200 points seems to be missing too, right? http://h4des.org/blog/index.php?/archives/344-Secuinside-CTF-Prequal-2014-Simple-login-web200-write-up.html

Oh, my bad :) Thanks!