> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/zh/ports-and-services/ftp-21.md).

# FTP - 21

FTP 枚举笔记，涵盖匿名访问、爆破检查、文件上传滥用、Web Shell 和反向 Shell。

当暴露匿名访问、可写目录、备份文件或 web 根目录上传时，FTP 往往会变得很有用。首先检查版本信息、匿名登录、写入权限，以及上传的文件是否可以从 Web 服务访问。

## 说明

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>暴力破解</strong></td><td>使用 Hydra 和字典验证 FTP 凭据。</td><td><a href="/zh/ports-and-services/ftp-21/ftp-brute-force-attack.md">FTP - 暴力破解攻击</a></td></tr><tr><td><strong>匿名访问</strong></td><td>检查匿名登录和可读取的 FTP 内容。</td><td><a href="/zh/ports-and-services/ftp-21/ftp-anonymous-attack.md">FTP - 匿名访问</a></td></tr><tr><td><strong>上传到 Shell</strong></td><td>滥用可写的 FTP 路径来获取 Web Shell 和反向 Shell。</td><td><a href="/zh/ports-and-services/ftp-21/ftp-reverse-shell-webshell-attack.md">FTP - 反向 Shell 和 Web Shell 攻击</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/zh/ports-and-services/ftp-21.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
