What's the feature 馃
The greatly appreciated #3336 arrived, but is missing one feature: no authentication combined with allowed IPs. Not all endpoints support authentication, but keeping a socks5 proxy just open to the wild seems unwise.
I would love something like SOCKS5_ALLOWED_IPS where I could define IPs such as 192.168.127.4,10.11.4.21 which are the only IPs being allowed for the socks5 proxy. This isn't better than using proper auth, but sometimes it is all we have. Probably related to #3336.
As a comparison, I am currently running a second docker container I would love to drop:
socks5-proxy:
image: serjs/go-socks5-proxy:v0.0.4
container_name: socks5-proxy
depends_on:
gluetun:
condition: service_started
network_mode: "service:gluetun"
environment:
REQUIRE_AUTH: "false"
ALLOWED_IPS: ${ALLOWEDIPS}
Extra information and references
No response
What's the feature 馃
The greatly appreciated #3336 arrived, but is missing one feature: no authentication combined with allowed IPs. Not all endpoints support authentication, but keeping a socks5 proxy just open to the wild seems unwise.
I would love something like
SOCKS5_ALLOWED_IPSwhere I could define IPs such as192.168.127.4,10.11.4.21which are the only IPs being allowed for the socks5 proxy. This isn't better than using proper auth, but sometimes it is all we have. Probably related to #3336.As a comparison, I am currently running a second docker container I would love to drop:
Extra information and references
No response