<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ntlm on The Manticore Project</title><link>https://themanticoreproject.com/tags/ntlm/</link><description>Recent content in Ntlm on The Manticore Project</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 17 Jun 2026 20:23:02 +0000</lastBuildDate><atom:link href="https://themanticoreproject.com/tags/ntlm/index.xml" rel="self" type="application/rss+xml"/><item><title>Manticore v1.1.5: Bug fixes</title><link>https://themanticoreproject.com/blog/manticore-v1-1-5-bug-fixes/</link><pubDate>Wed, 17 Jun 2026 20:23:02 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-5-bug-fixes/</guid><description>&lt;p>Manticore is a Go library of offensive and defensive security primitives maintained by The Manticore Project. This release, v1.1.5, is a maintenance update with no new features: it is a round of bug fixes focused on the LDAP and SMB clients, following the RPC work that landed in v1.1.4. The fixes fall into a few categories.&lt;/p>
&lt;h2 id="pass-the-hash-correctness-on-ldap-and-smb">Pass-the-hash correctness on LDAP and SMB&lt;/h2>
&lt;p>Two of the fixes correct pass-the-hash, on both the LDAP and the SMB stacks. LDAP pass-the-hash now performs an NTLM hash bind rather than treating the hash as a password (#657), and SMB NTLM authentication now uses the NT hash for the pass-the-hash path (#679). In both cases the supplied hash was not being fed into the right step of the NTLM exchange, so authentication from a harvested hash failed where it should have succeeded. If you authenticate with NT hashes against either protocol, this is the release you want.&lt;/p></description></item><item><title>Manticore v1.1.4: RPC improvements</title><link>https://themanticoreproject.com/blog/manticore-v1-1-4-rpc-improvements/</link><pubDate>Wed, 17 Jun 2026 10:49:11 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-4-rpc-improvements/</guid><description>&lt;p>Manticore is the Go library of offensive and defensive security primitives that underpins the tools of The Manticore Project: protocol stacks, cryptography, parsers, and the wire structures you need when you cannot rely on a host&amp;rsquo;s native client. The v1.1.0 release brought SMB 2.0 and the first DCE/RPC and endpoint-mapper layers; this release builds those out into something you can actually point at a domain.&lt;/p>
&lt;p>&lt;strong>v1.1.4 is an RPC-focused release.&lt;/strong> It fills in endpoint-mapper enumeration, teaches the stack to decode protocol towers for every common transport, adds a curated catalog of well-known interfaces, brings authenticated binds with pass-the-hash, and lands the MS-DRSR replication blob structures. The sections below group the work by theme.&lt;/p></description></item><item><title>Manticore v1.1.0: Introducing SMB 2.0</title><link>https://themanticoreproject.com/blog/manticore-v1-1-0-introducing-smb-2-0/</link><pubDate>Thu, 11 Jun 2026 14:23:43 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-0-introducing-smb-2-0/</guid><description>&lt;p>Manticore is the Go library of offensive and defensive security primitives that underpins the tools of The Manticore Project: protocol stacks, cryptography, parsers, and the wire structures you need when you cannot rely on a host&amp;rsquo;s native client. Until now, the SMB stack in Manticore was effectively SMB1-only. That is enough to talk to legacy targets, but it leaves out the dialect that has been the default on Windows for more than a decade.&lt;/p></description></item></channel></rss>