-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
same issue too. |
1 similar comment
same issue too. |
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. |
Even with this env variable I still get tons of "[proxychains] DLL init: proxychains-ng 4.17" in logs. |
i don't. can you paste your terminal input and ouput ? |
Sorry for late answer. Here is the output:
And to be sure:
|
you're using sudo, that's the reason. for setuid binaries the environment is cleared as a security measure, so the env variable you set doesn't even make it to proxychains, and proxychains itself likely doesn't do anything at all except printing that message and then failing to hook the different subprocesses. |
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.The text was updated successfully, but these errors were encountered: