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 · 7 comments
Open

quiet_mode in proxychains.conf does not work #549

zeertzjq opened this issue Jan 21, 2024 · 7 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.

@samehraban
Copy link

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.

@rofl0r
Copy link
Owner

rofl0r commented Jan 19, 2025

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 ?

@samehraban
Copy link

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:

~ sudo proxychains apt update
[proxychains] config file found: /etc/proxychains4.conf
[proxychains] preloading /usr/lib/x86_64-linux-gnu/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
0% [Working][proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
Hit:1 http://ir.archive.ubuntu.com/ubuntu noble InRelease
Ign:2 https://packages.microsoft.com/repos/code stable InRelease                                
Hit:3 http://ir.archive.ubuntu.com/ubuntu noble-updates InRelease                               
Hit:4 http://ir.archive.ubuntu.com/ubuntu noble-backports InRelease 
Hit:5 http://security.ubuntu.com/ubuntu noble-security InRelease
Ign:6 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 https://packages.microsoft.com/repos/code stable InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable InRelease
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
41 packages can be upgraded. Run 'apt list --upgradable' to see them.

And to be sure:

~ echo $PROXYCHAINS_QUIET_MODE
1

@rofl0r
Copy link
Owner

rofl0r commented Jan 26, 2025

sudo proxychains apt update

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.
as a workaround, you can do sudo bash, and then run proxychains4 apt update without -q to make sure it does connections over your proxy, and when that works you can try to wire up your env variable or just run proxychains4 with -q.

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

5 participants