Improve the .ctf/config structure

[ColdHeat]

I do not like the structure of the current ctf config. It's too basic. For example the yaml_path issue is difficult to solve because challenge keys are simple key value stores. Instead of trying to shoehorn things on top of the kv, we should break it up into more complex sections.

I think if it's possible something like this would be superior:

[challenges]
[test/test]
location = git@git
path = challenge.yml

We would need:

1. A way to detect old .ctf/configs and change behvior based on that
2. Extract the parsing behavior for both type of configs into seperate functions.

[ColdHeat]

I think this involves a conversion from configparser to toml.

[challenge."asdf/asdf"]
name = "Nail"

[http.cookies]
asdf = "asdf"

Ideas like this seem to work with toml which allows us to keep existing functionality while getting more organization.

[MilyMilo]

Toml has been vendored inside the standard library starting with 3.11 so I feel like it's the right direction. Also it's a superior format to ini which would make for more explicit configs.

[noah-de]

I am interested in the discussion of a new .ctf/config structure.

Would new structure keep the version at the bottom of the file as is in the current spec? It's currently listed under 'optional', but if included, could provide an indicator as to how a file should be parsed.

[ColdHeat]

@noah-de I think version should be considered a required field. Feel free to drop any thoughts here. Sorry for the delay I feel like I never got an email for your message.

[ColdHeat]

We now need to support the new [instance] [media] sections. There could also be some consideration of adding a pages section but its not super important.

[R1ckyH]

Maybe record challenge id with path can be a good method to achieve changing challenge name?

[ColdHeat]

@R1ckyH Where would you want to store this? In the config file you're saying?

[R1ckyH]

@R1ckyH Where would you want to store this? In the config file you're saying?

@ColdHeat One possible solution may be stored in the challenge folder using ctfcli challenge install. and keep using the chal location store at the /.ctf/config in /.ctf/config we can change the store structure:

current:

[challenges]
path = path

future:

[challenges]
chal_id = path

which ID is synced with ctfd's chal id

when changing the challenge(maybe with a command challenge rename?), just change the location store in /.ctf/config

About the chal config, I know that currently is a bit difficult to identify the path change.

So we can use .config in chal folder to record some of the details from the ctfd instance for example, chal_id which chal id can be used to identify the challenge for sync/install challenge again when the user not using the ctfcli command to do any rename(either folder or challenge.yaml rename).

Here is one of the example of chal config

+.ctf
 |  > .config
+ crypto
 |  + chal_1
     |  > .config