felixbade / ctf-platform Goto Github PK

Not a must but could be useful. At least the channel id(s) and which notifications they receive. Secret token can be in a text file / configuration for now.

Or then the notification types can be hardcoded and channel id(s) and secret token are read from .env

Right now the system assumes that

1. numbers start from zero
2. there are no duplicates
3. there are no gaps

Currently changing the order violates at least 2 or 3 as the order changing is not atomic.

• Add challenge folder structure
• Add a route that works for multiple challenges
• Add a template that contains brief, URI and flag check form
• Check if the flag is correct
• If yes, redirect to the challenge's "solved" page

Scope

• stateless
• loginless
• no scoreboard
• no navigation between challenges

Details TBD. Could be that it's a box of text that the user can see permanently + edit later. Unique to player + challenge.

e.g. ”52 minutes ago”, ”today at 14:52”

The user should be able to access only the next uncompleted challenge, and the challenges they have completed. This feature requires keeping track which challenges which users has done (related to #10)

Ideally the function would be available in templates as well

It's a bit confusing (possibly postponing challenge creation) and there's no reason to have it anything else than the default value (last in the list)

Remove order number field from individual challenge edit form and make a separate form that has the order numbers from all challenges at once.

Navigation to this page could be from the main admin view through a text ”change order”

Maybe to a main scoreboard?

For example right now navigation from scoreboard to the frontpage is not possible without editing the URL.

get_challenge_list in app/controllers/challenge.py should use db, not order.txt

Makes it easier to do other things that relate to different challenges (e.g. scoreboard and progress tracking)

Might not be necessary for the first version

E.g. separated by line breaks

could be either for just admins or for a more public channel (can be mentioned in welcome.md)

Current implementation relies on the fact that one user is named admin. Instead we should have a field that determines if a user is an administrator or not.

E.g. zip or json

Not in scope:

• getting to the first challenge
• what happens after the last challenge is solved