Exit with error message if -proxy
is specified without arguments (instead of continuing without proxy server).
Continuing without a proxy server when the end-user has specified -proxy
may result in accidental loss of privacy. (The end-user might think he/she is using a proxy when he/she is not.)
Before this patch:
0$ src/bitcoind -proxy
1…
22020-09-23T00:24:33Z InitParameterInteraction: parameter interaction: -proxy set -> setting -listen=0
32020-09-23T00:24:33Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
42020-09-23T00:24:33Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
52020-09-23T00:24:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
6…
72020-09-23T00:24:33Z init message: Starting network threads...
bitcoind
is now running without a proxy server (GetProxy(…, …) == false
, HaveNameProxy() == false
, etc.).
Note that the “-proxy set” log messages above which the end-user might interpret as “good, my traffic is now routed via the proxy”.
After this patch:
0$ src/bitcoind -proxy
1Error: No proxy server specified. Use -proxy=<ip> or -proxy=<ip:port>.
2$ echo $?
31