> 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/kerberos/kerberos-observation-with-wireshark.md).

# 使用 Wireshark 观察 Kerberos

针对使用 Wireshark 观察 Kerberos 的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。

### 观察一次认证

我们打开 Wireshark，然后使用一个用户连接，例如：

```
user1
```

在 Wireshark 中，你可以使用以下方式过滤 Kerberos 流量：

```
kerberos
```

然后我们观察这些交换：

```bash
AS-REQ
AS-REP
TGS-REQ
TGS-REP
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-90df44f66d6cbc4719e40f3d26cd2b2673f97392%2F%7BBB1E1E17-1E72-4CFA-9A55-5C93C28496AC%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

### 无权限访问共享的示例

从 `user2`，我们尝试访问一个管理共享：

```
cd //WS01/C$
```

在 Wireshark 中，我们可以观察到：

```
TGS-REQ
TGS-REP
SMB 访问被拒绝
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-353387bfc535308105528a3ae872608bf3f57671%2F%7BBEAA2E5F-3867-4FF0-8690-E2E5E50AF4F8%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

这意味着：

1. 用户请求服务票据；
2. KDC 签发该票据；
3. 将票据出示给服务器；
4. 服务器由于 SMB 或 NTFS 权限而拒绝访问。

### 票据与认证器

访问服务时，客户端通常会发送：

* 一个服务票据；
* 一个认证器。

该票据证明 KDC 已授权访问该服务。

认证器证明使用该票据的确实是该客户端。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-48cdc3fab929a2114c6b35cc7d41f53cdb9cd9f0%2F%7B1F228000-B616-47CB-B34B-20A5DB584B21%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/kerberos/kerberos-observation-with-wireshark.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.
