Missing files in some challenges

[terryyz]

There are some challenges missing required files that have been mentioned by the REHOST.md file.

For example, the REHOST file of this challenge mentioned two files. diethard and diethard.rb. However, the current folder only contains diethard, which means we need to download the diethard.rb and place it inside.

[terryyz]

Hi @prathamgupta36,

May I know when this issue could be resolved? Thanks!

[prathamgupta36]

I was working on organizing which challenges are affected and once thats done it should just be adding files in those. I did see that a couple of the challenges which did not have files from src were because those files were not distributed during the ctf which I don't think I should add.

[terryyz]

Thanks!
BTW, is there a way to determine all the verified tasks (where the flags can be properly captured)?
For some tasks, containing flagCheck or .flag.sha256 doesn't necessarily mean that they are fully verified..?

[prathamgupta36]

I am not sure I understand what you mean by verified tasks, could you explain?

[terryyz]

I am not sure I understand what you mean by verified tasks, could you explain?

I was referring to the CTF challenge used to obtain the valid flag (which is verified using either flagCheck or .flag.sha256), assuming the environment has been configured correctly.

[prathamgupta36]

If a challenge does not contain flagCheck then it is solvable using the files which have been modified to extract the pwn.college flag rather than the static ones provided during the CTF. In that case the challenge looks for /flag since thats where the pwn.college flag is stored.

[terryyz]

Thanks!

Some follow-up questions:

1. Can we still use .flag.sha256 to validate the flags?
2. Are we meant to always create flag by ourselves and set the permission as 400 when rehosting the challenge (if .flag.sha256 is not given) locally?

[prathamgupta36]

You can use .flag.sha256 to validate the flags but my suggestion would be to use flagCheck whenever possible and yes you are supposed to create the flag if you use the files rehosted on ctf-archive as they always point to /flag to extract the flag.

[terryyz]

But for the challenges having .flag.sha256, they are supposed to be the static flags..? In this case, I don't need to create any flags, since I don't know the flag context, right?