Sending input to stdin does not work when doing remote debugging from macOS to Linux
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
While working with this ctf challenge, I noticed that sending input to stdin does not work when doing remote debugging. The target runs on a Linux box and I connected to it from macOS. After the target asks for input, and I typed something into the console, the target does not stop. Interrupting the target, I can see it is still waiting for input, which means the input was not sent to stdin.
This is a rust binary, not sure it it is relevant.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the remote-debugging scenario from macOS to Linux using the attached wargame.zip Rust binary. Trace the stdin path after the target requests input and verify that console input reaches the waiting process; done means the target receives input and continues normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100