Commit 8fd09dc9a25fb673426340a23794df7f11a44010 adds SOCKSv5-over-UNIX-socket proxy and starts it "whenever ebuilds are started with network-sandbox enabled".
I do not use distcc and do not want any holes in network sandbox. Please add ability to disable this proxy and consider disabling it by default or at least when distcc is disabled in FEATURES.
Created attachment 402766 [details, diff]
Attached patch works fine for me with portage-2.2.18: it builds, all tests work fine, FEATURES='-network-sandbox network-sandbox-proxy', FEATURES='network-sandbox network-sandbox-proxy' and FEATURES='network-sandbox' work as expected.
For me 'python3.3 /usr/lib/portage/python3.3/socks5-server.py /var/tmp/.portage.27962.net.sock' is now running only when both network-sandbox and network-sandbox-proxy are enabled. It should also run when network-sandbox and distcc are enabled, but i did not check.
applied in git commit 1f94508e9adeffd7170cb23852ae40fc1f8b6c98
Released in portage-2.2.19