Mercurial > kallithea
diff docs/setup.rst @ 8886:3d7ba590f6f5
auth: only use X- headers instead of REMOTE_ADDR if explicitly told so in remote_addr_header
Before, X-Forwarded-For (and others) headers would *always* be trusted blindly,
also in setups without a proxy server. It would thus in some cases be
possible for users to fake their IP, and thus potentially be possible to bypass
IP restrictions configured in Kallithea.
Fixed by making it configurable which WSGI environment variable to use for the
remote address. Users can configure remote_addr_header to for example
HTTP_X_FORWARDED_FOR instead of using the default REMOTE_ADDR.
This change is a bit similar to what is going on in the https_fixup middleware,
but is doing a bit more of what for example is happening in similar code in
werkzeug/middleware/proxy_fix.py .
| author | Mads Kiilerich <mads@kiilerich.com> |
|---|---|
| date | Sun, 09 May 2021 22:34:02 +0200 |
| parents | 883a0c6c425f |
| children | 070b8c39736f |
line wrap: on
line diff
--- a/docs/setup.rst Sun May 09 22:32:51 2021 +0200 +++ b/docs/setup.rst Sun May 09 22:34:02 2021 +0200 @@ -423,8 +423,12 @@ configured to pick that information up and trust it. Kallithea will by default rely on its WSGI server to provide the IP of the -client in the WSGI environment as ``REMOTE_ADDR``, but it can also -get it from the ``X-Real-IP`` or ``X-Forwarded-For`` HTTP headers. +client in the WSGI environment as ``REMOTE_ADDR``, but it can be configured to +get it from an HTTP header that has been set by the proxy server. For +example, if the proxy server puts the client IP in the ``X-Forwarded-For`` +HTTP header, set:: + + remote_addr_variable = HTTP_X_FORWARDED_FOR Kallithea will by default rely on finding the protocol (``http`` or ``https``) in the WSGI environment as ``wsgi.url_scheme``. If the proxy server puts