> 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/ja/ports-and-services/kerberos-88/kerbrute-tool.md). # Kerbrute - ツール Kerbruteと生成したユーザー名ワードリストを使ったKerberosユーザー列挙。 > Kerbruteは、Kerberosドメインでユーザー列挙を実行するために設計されたオープンソースツールです。KDC（Key Distribution Center）サービスからの応答を利用して、有効なユーザーを特定します。 ### **Kerberosによるユーザー列挙** その `users.txt` ファイルには、さまざまな名前の形式（名、姓、イニシャルなど）を組み合わせて生成された、候補ユーザー名の一覧が含まれています。これらの形式により、Active Directoryドメインで有効なユーザーを特定できる可能性が高まります。

#### 作成する `users.txt` 候補ユーザー名を含むファイル ``` hugosmith h.smith hugo.smith hsmith fergussmith f.smith fergus.smith fsmith hugobear h.bear hugo.bear hbear stevenkerb s.kerb steven.kerb skerb shauncoins s.coins shaun.coins scoins bowietaylor b.taylor bowie.taylor btaylor sophiedriver s.driver sophie.driver sdriver ``` 使用する `kerbrute` 有効なユーザーを列挙するために使用します。 ```bash kerbrute userenum -d egotistical-bank.local --dc 10.10.10.175 users.txt ```

**事前定義された辞書を使った操作** Kerbruteは、SecListsのような公開辞書でも使用できます： * **追加オプション**: * `/usr/share/SecLists/Usernames/xato-net-10-million-usernames.txt`：何百万もの候補ユーザー名を含む辞書を使用します。

kerbrute userenum -d support.htb --dc 10.10.11.174 /usr/share/SecLists/Usernames/xato-net-10-million-usernames.txt

--- # 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/ja/ports-and-services/kerberos-88/kerbrute-tool.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.