问题原文
原帖链接 · gelonida · CC BY-SA 4.0
I'm having one server, that is behind a reverse proxy, that I don't control. I'd like to use fail2ban to block nginx traffic under certain conditions.
normally fail2ban useses iptables to block traffic originating from the intruder's IP
However my server is behind a reverse proxy and from my server's point of view all traffic originates from the reverse proxy:
I found following url https://forums.freebsd.org/threads/fail2ban-behind-a-proxy.55041/
that suggests tu use iptables with package intropspection like for example:
actionban = iptables -I fail2ban-<name> 1 -p tcp --dport 80 -m string --algo bm --string 'X-Forwarded-For: <ip>' -j DROP
However the reverse proxy that I cannot control forwards the traffic as https traffic, meaning, that I cannot introspect the traffic for X-Forwarded-For headers as they would be encrypted.
Thus my question.
Do others have a similar scenario and is there an existing actionban = that adds Deny rules to nginx ?
Or do I have to handcraft a script trying to do this (edit nginx the nginx configuration and reload nginx)
What other solution would allow me to tell nginx dynamically which requests (containing specific X-Forwarded-For: headers) to block
社区高分解答
原帖链接 · sebres · CC BY-SA 4.0
You could use fail2ban action nginx-block-map, see nginx-block-map.conf for details.
Just note that by filtering of X-Forwarded-For header, it is pretty simple for the intruders to manipulate the request to avoid a ban (with setting of the different values each new request in this header). The question whether an intruder siting behind the proxy or just simulating the proxy, and just set the header X-Forwarded-For by itself can't be answered simply.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
