Skip to content
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

PR for Issue#1236 #1833

Open
wants to merge 32 commits into
base: master
Choose a base branch
from
Open

Conversation

Pastekitoo
Copy link

@Pastekitoo Pastekitoo commented Feb 7, 2025

I need help please, you can read some informations in the TestChallenge52 folder with README.txt file.

What kind of changes does this PR include?

  • Fixes or refactors
  • A new challenge
  • Additional documentation
  • Something else

Description

Relations

References

Checklist:

  • All the contributions made are solely the work of me and my co-authors
  • I tested the changes in this PR (if applicable)
  • I added unit tests to ensure my change works (when change in Java or on front-end code)
  • I added UI tests to ensure my UI changes work (when change in the overall UI, not needed if just adding a challenge)
  • The PR passes pre-commit hooks and automated tests

@@ -0,0 +1,13 @@
#Problem
I added the binary file in the docker image and I can execute it but I can't use gdb on the process.
The binary file is not in the final container.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not in the WrongSecrets container? Should I try to create one with it?

I added the binary file in the docker image and I can execute it but I can't use gdb on the process.
The binary file is not in the final container.

Even with 1 in proc/sys/kernel/yama/ptrace_scope and the process launched by the user wrongsecrets, I can't use gdb on it.(in the docker image and in the kubernetes container)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can test this next weekend :-)

We can now attach a debug container to the main container.
Then we can use gdb -p <PID> and use p &secret to get the variable's memory address of secret.

I used a specific secret here for the test but later we will be able to use rand() to have a random secret.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants