2022-08-01 17:36:50 +02:00
|
|
|
|
---
|
|
|
|
|
|
date: "2022-08-01T00:00:00+00:00"
|
2023-04-06 11:06:32 +02:00
|
|
|
|
title: "设置 Fail2ban"
|
2022-08-01 17:36:50 +02:00
|
|
|
|
slug: "fail2ban-setup"
|
|
|
|
|
|
weight: 16
|
|
|
|
|
|
toc: false
|
|
|
|
|
|
draft: false
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 05:33:41 +02:00
|
|
|
|
aliases:
|
|
|
|
|
|
- /zh-cn/fail2ban-setup
|
2022-08-01 17:36:50 +02:00
|
|
|
|
menu:
|
|
|
|
|
|
sidebar:
|
2023-03-23 16:18:24 +01:00
|
|
|
|
parent: "administration"
|
2022-08-01 17:36:50 +02:00
|
|
|
|
name: "设置 Fail2ban"
|
|
|
|
|
|
weight: 16
|
|
|
|
|
|
identifier: "fail2ban-setup"
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
# 使用 Fail2ban 阻止攻击者的暴力登录
|
|
|
|
|
|
|
|
|
|
|
|
**Fail2ban 检查客户端登录日志，将多次登录失败的客户端识别为攻击者并在一段时间内阻止其访问服务。如果你的实例是公开的，这一点尤其重要。请管理员仔细设置 fail2ban，错误的配置将导致防火墙阻止你访问自己的服务器。**
|
|
|
|
|
|
|
|
|
|
|
|
Gitea 会在日志文件 `log/gitea.log` 中记录登录失败的 CLI、SSH 或 HTTP 客户端 IP 地址，而你需要将 Gitea 的日志输出模式从默认的 `console` 更改为 `file`。这表示将日志输出到文件，使得 fail2ban 可以定期扫描日志内容。
|
|
|
|
|
|
|
|
|
|
|
|
当用户的身份验证失败时，日志中会记录此类信息：
|
|
|
|
|
|
|
|
|
|
|
|
```log
|
|
|
|
|
|
2018/04/26 18:15:54 [I] Failed authentication attempt for user from xxx.xxx.xxx.xxx
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
```log
|
|
|
|
|
|
2020/10/15 16:08:44 [E] invalid credentials from xxx.xxx.xxx.xxx
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## 设置 Fail2ban
|
|
|
|
|
|
|
|
|
|
|
|
添加日志过滤器规则到配置文件 `/etc/fail2ban/filter.d/gitea.conf`:
|
|
|
|
|
|
|
|
|
|
|
|
```ini
|
|
|
|
|
|
[Definition]
|
|
|
|
|
|
failregex = .*(Failed authentication attempt|invalid credentials|Attempted access of unknown user).* from <HOST>
|
|
|
|
|
|
ignoreregex =
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
添加监狱规则到配置文件 `/etc/fail2ban/jail.d/gitea.conf`:
|
|
|
|
|
|
|
|
|
|
|
|
```ini
|
|
|
|
|
|
[gitea]
|
|
|
|
|
|
enabled = true
|
|
|
|
|
|
filter = gitea
|
|
|
|
|
|
logpath = /var/lib/gitea/log/gitea.log
|
|
|
|
|
|
maxretry = 10
|
|
|
|
|
|
findtime = 3600
|
|
|
|
|
|
bantime = 900
|
|
|
|
|
|
action = iptables-allports
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
如果你的 Gitea 实例运行在 Docker 容器中，并且直接将容器端口暴露到外部网络，
|
|
|
|
|
|
你还需要添加 `chain="FORWARD"` 到监狱规则配置文件 `/etc/fail2ban/jail.d/gitea-docker.conf`
|
|
|
|
|
|
以适应 Docker 的网络转发规则。但如果你在容器的宿主机上使用 Nginx 反向代理连接到 Gitea 则无需这样配置。
|
|
|
|
|
|
|
|
|
|
|
|
```ini
|
|
|
|
|
|
[gitea-docker]
|
|
|
|
|
|
enabled = true
|
|
|
|
|
|
filter = gitea
|
|
|
|
|
|
logpath = /var/lib/gitea/log/gitea.log
|
|
|
|
|
|
maxretry = 10
|
|
|
|
|
|
findtime = 3600
|
|
|
|
|
|
bantime = 900
|
|
|
|
|
|
action = iptables-allports[chain="FORWARD"]
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
最后，运行 `systemctl restart fail2ban` 即可应用更改。现在，你可以使用 `systemctl status fail2ban` 检查 fail2ban 运行状态。
|
|
|
|
|
|
|
|
|
|
|
|
上述规则规定客户端在 1 小时内，如果登录失败的次数达到 10 次，则通过 iptables 锁定该客户端 IP 地址 15 分钟。
|
|
|
|
|
|
|
|
|
|
|
|
## 设置反向代理
|
|
|
|
|
|
|
|
|
|
|
|
如果你使用 Nginx 反向代理到 Gitea 实例，你还需要设置 Nginx 的 HTTP 头部值 `X-Real-IP` 将真实的客户端 IP 地址传递给 Gitea。否则 Gitea 程序会将客户端地址错误解析为反向代理服务器的地址，例如回环地址 `127.0.0.1`。
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
proxy_set_header X-Real-IP $remote_addr;
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
额外注意，在 Gitea 的配置文件 `app.ini` 中存在下列默认值：
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
REVERSE_PROXY_LIMIT = 1
|
|
|
|
|
|
REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
`REVERSE_PROXY_LIMIT` 限制反向代理服务器的层数，设置为 `0` 表示不使用这些标头。
|
|
|
|
|
|
`REVERSE_PROXY_TRUSTED_PROXIES` 表示受信任的反向代理服务器网络地址，
|
|
|
|
|
|
经过该网络地址转发来的流量会经过解析 `X-Real-IP` 头部得到真实客户端地址。
|
|
|
|
|
|
（参考 [configuration cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/#security-security)）
|
