-
Notifications
You must be signed in to change notification settings - Fork 16
Added Cryptography Modules #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ["/challenge/run.py"], | ||
| stdout=subprocess.PIPE, | ||
| text=True, | ||
| ) | ||
| assert "TASK:" in p.stdout.readline() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aes-cbc test expects nonexistent TASK prefix
The aes-cbc public test asserts the first line from /challenge/run.py contains "TASK:", but the template used by that run script (common/crypto_aes_cbc_simple.py.j2) prints only the AES key and ciphertext headers, never a TASK prefix. As written the assertion will always fail on the very first read, so the challenge can't pass its own public tests.
Useful? React with 👍 / 👎.
| proc = subprocess.Popen( | ||
| ["/challenge/crypto.py"], | ||
| stdin=subprocess.PIPE, | ||
| stdout=subprocess.PIPE, | ||
| stderr=subprocess.PIPE, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Crypto challenges invoke missing crypto.py entrypoint
Multiple public tests (sha, sha2, tls, rsa3, rsa4) spawn /challenge/crypto.py, but each challenge only ships a run.py generated from crypto_levels.py.j2, so subprocess.Popen will hit ENOENT before any challenge logic runs. Either the tests need to call run.py or the build needs to install the binary under the expected name; in the current commit these tests cannot succeed because the referenced executable is absent.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh shoot, I must have made this typo while copy pasting stuff between files.
Added all the cryptography challenges to the monorepo and added the public tests as well