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

quiet_mode in proxychains.conf does not work #549

Open
zeertzjq opened this issue Jan 21, 2024 · 3 comments
Open

quiet_mode in proxychains.conf does not work #549

zeertzjq opened this issue Jan 21, 2024 · 3 comments

Comments

@zeertzjq
Copy link

With proxychains 4.17, specifying quiet_mode in /etc/proxychains.conf does not silence the [proxychains] DLL init: proxychains-ng 4.17 message. It can only be silenced by the -q command line argument.

@fyangami
Copy link

same issue too.

1 similar comment
@TimeRainStarSky
Copy link

same issue too.

@rofl0r
Copy link
Owner

rofl0r commented Feb 9, 2024

it's a difficult problem. at the point the config is parsed, these messages were already printed. i'd have to implement some sort of caching (involves memory allocation) and postpone printing of the output until config parsing is done. memory allocation in a hook library can lead to all sorts of issues in multithreaded/multiprocess (fork()ing) apps, that's why most (or all, in case the threaded resolver is disabled) memory is statically allocated. therefore my leaning is to obsolete the config option and recommend instead the use of -q or setting the environment variable PROXYCHAINS_QUIET_MODE=1 instead. even though the output of proxychains may appear annyoing to you, it's the only way to make sure the program is properly hooked.

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

No branches or pull requests

4 participants