rofl0r / rofl0r/proxychains-ng
change env variables during execution
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Does this new generation proxychains do something with environment variables. It seems that some of the programs that I am running with proxychains-ng and which read environment variables are no longer working because proxychains-ng wouldn't let it read the env variables.
Though I never faced this problem with proxychains 3.1
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 environment-variable behavior with proxychains-ng and compare it with proxychains 3.1, using a program that reads environment variables. Trace where proxychains-ng affects that program's execution and identify whether the variables are being blocked or changed. Done means the affected programs can read the expected environment variables without breaking proxying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100