add proxychains-cli to help using inline config

[0x0a0d]

• add env PROXYCHAINS_CONFIG_FD= to proxychains4 that will be used to get content and parse before using file parsing (default behavior)
• add proxychains-cli that take and parse inline config to fd(3) then pipe to proxychains4
• add cli test in /tests/cli/test-cli.sh
• add uninstall to Makefile
• add _proxychains-cli to complications/zsh
• more details read more on README-CLI.md

Options

Option	Default	Description
-h, --help		Print help and exit
-v, --version		Print version and exit
-c, --chain MODE	strict	Chain mode: strict/dynamic/random/round_robin
-l, --chain-len N		Chain length (for random/round_robin)
-q, --quiet		Quiet mode
-d, --dns MODE	proxy	DNS: proxy/old/off/IP:PORT
-S, --dns-subnet N	224	Remote DNS subnet (0-255)
-R, --read-timeout MS	15000	TCP read timeout (ms)
-T, --connect-timeout MS	8000	TCP connect timeout (ms)
-n, --localnet CIDR		Bypass proxy for CIDR (repeatable)
--dnat "SRC DST"		DNAT mapping (repeatable)
-P, --proxy "IP PORT [ USER PASS ]"		Add proxy (repeatable)
--config		Print config and exit
--proxychains-path PATH	proxychains4	Path to proxychains4 binary

[rofl0r]

which fd it's using is irrelevant to a user, it's an implementation detail

[0x0a0d]

I forgot to update this README, when using fd, I can not pass content to child process in this case:

1. main.c exec node (nodejs) with PROXYCHAINS_CONFIG_FD=3
   ↓
2. dyld loads libproxychains4.dylib (DYLD_INSERT_LIBRARIES)
   ↓
3. gcc_init() constructor run BEFORE main()
   ↓
4. do_init() → get_chain_data() → setenv("PROXYCHAINS_CONFIG_FD", "5", 1) (nodejs used fd 3, 4 => we use 5)
   ↓
5. [proxychains] DLL init: proxychains-ng...  ← log printed
   ↓
6. node main() started
   ↓  
7. Debugger listening...  ← node start debugger
   ↓
8. [proxychains] failed to read... ← debugger subprocess still see PROXYCHAINS_CONFIG_FD is 3

it happened because

┌─────────────────────────────────────────────────────────────┐
│ Library loading (before main)                               │
├─────────────────────────────────────────────────────────────┤
│ 1. libc.dylib loads                                         │
│ 2. libnode.dylib loads ──► Node's C++ static init           │
│    └── NodeJS snapshot environment HERE!                    │
│ 3. libproxychains4.dylib loads                              │
│    └── run, clone fd, write new value to env but late       │
└─────────────────────────────────────────────────────────────┘
                    ↓
              main() starts

ofcourse I can use a larger fd() but not sure that program dont use that fd
=> I decided to use env PROXYCHAINS_CONFIG_DATA_ENV_VAR to handle config data
will update README

[rofl0r]

you mean the issue is the quiet mode ? just pass the right env var just like main.c does then

[0x0a0d]

It's not related to quiet mode.
proxychains4 uses env var to pass data to libproxychains, which is injected and runs before the program's main().
Everything works when the program doesn't spawn child processes, example: I'm using fd3 with PROXYCHAINS_DATA_FD=3.
But when the main program creates child processes, it may forward fd3/fd4 to them. In that case, I must switch libproxychains to use fd5 to avoid conflict with the child process behavior, and update the env to PROXYCHAINS_DATA_FD=5.
The issue when use proxychains to run Node.js (node) in debug mode:
node takes a snapshot of all env at startup and uses that snapshot for all child processes. As a result, child processes still receive PROXYCHAINS_DATA_FD=3 instead of 5, causing parsing errors.

[rofl0r]

i see. will think about the best solution for that.

[rofl0r]

imo we should only advertise protocol://[user:pass@]ip:port syntax in the cli tool

[0x0a0d]

ok lets implement this

[0x0a0d]

implemented in proxychains4-cli, take a look
https://github.com/rofl0r/proxychains-ng/pull/610/files#diff-69fcc264dd1c66e96beb0fc7c26abb4947649d95ad777a2301adb8dd532f4577R72-R128

[0x0a0d]

@rofl0r should cli resolve hostname if URL using hostname:port instead of ip:port?

[rofl0r]

ok, as usual all your AI generated content again makes this a huge PR, which takes every reload take half a minute. for now, exclude all your README and zsh etc additions until we got the proxychains4-cli, Makefile, and libproxychains.c right so i dont have to waste my time with secondary stuff until the primary stuff is right.