<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on 🕵 1dnu11</title><link>https://1dnu11.github.io/blog/</link><description>Recent content in Blog on 🕵 1dnu11</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright © 2024, 1dnu11.</copyright><lastBuildDate>Sat, 23 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://1dnu11.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Credential Dumping</title><link>https://1dnu11.github.io/windows-credential-dumping/</link><pubDate>Sat, 23 Mar 2024 00:00:00 +0000</pubDate><guid>https://1dnu11.github.io/windows-credential-dumping/</guid><description>Windows Password Hashes Windows stores hashes user account passwords locally in the SAM (Security Accounts Manager) database. Authentication and verification of user credentials is facilitated by the LSA (Local Security Authority).
SAM Database SAM is a database file that manages user accounts and passwords. All passwords stored in SAM are hashed. This database cannot be copied while the operating system is running. Windows NT keeps the SAM db file locked. Attackrs tipically use in-memory techniques to dump SAM hashes from the LSASS process.</description></item></channel></rss>