-
-
Notifications
You must be signed in to change notification settings - Fork 803
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
Remove trusted proxies #2229
Remove trusted proxies #2229
Conversation
This is a nuclear approach. Normally, we'd mark it as deprecated and warn users about the pending removal. How certain are you that this is not being used? I think we're better off giving users the tools they need to tailor security to their needs. |
I'm fairly convinced that the few people that have set the option don't understand why they did or are doing so needlessly. Most people set up a reverse proxy like this, where the reverse proxy is on the same network as the stash host:
However, the trusted proxies setting is to allow people to create setups like this, where the proxy is accessing stash through the internet. This is an exotic setup, tricky to get right, and requires you to set up firewall rules to allow the proxy to do this:
|
FYI, if somebody does have this setup, they can simply not pass X-forwarded-for, and retain the old functionality as a workaround |
This option was removed in stashapp/stash#2229
Trusted proxies in its current form is near useless, and perhaps encourages bad practices.
It allows a connection from a proxy on the public internet to forward requests into stash. 99% of reverse proxies are running on the same host, and the other 1% are a load balancer or bastion host running on the same network or VPC. I can't figure a use case for this, and I thought the same when I was implementing it. It only came up because of a 'what if' on code review, but I think we should thin it down.