<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Smb on The Manticore Project</title><link>https://themanticoreproject.com/tags/smb/</link><description>Recent content in Smb 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/smb/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.1: A Windows REG file parser, NDR64, and Remote Registry</title><link>https://themanticoreproject.com/blog/manticore-v1-1-1-windows-reg-file-parser/</link><pubDate>Tue, 16 Jun 2026 06:41:06 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-1-windows-reg-file-parser/</guid><description>&lt;p>Manticore is the Go library of offensive and defensive security primitives that The Manticore Project&amp;rsquo;s tools are built on: SMB, LDAP, Kerberos, DCE/RPC, and the Windows data types that hold them together. Most of the work in a release like this happens below the surface, in the wire encoders that have to match exactly what a real Windows server expects.&lt;/p>
&lt;p>In &lt;strong>v1.1.1&lt;/strong> I focused on three things: bringing the NDR codec up to NDR64 so DCE/RPC interfaces negotiate the transfer syntax modern Windows servers prefer, landing a new &lt;code>ms_rrp&lt;/code> package with a Remote Registry client and a real Windows &lt;code>.reg&lt;/code> file parser, and a handful of correctness improvements around Kerberos SPNs, SMB security descriptors, and GUID handling.&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><item><title>Manticore v1.0.9 - Complete SMBv1, NDR 2.0, and the first RPC interfaces</title><link>https://themanticoreproject.com/blog/manticore-v1.0.9-release/</link><pubDate>Tue, 09 Jun 2026 12:46:25 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1.0.9-release/</guid><description>&lt;p>We tagged &lt;a href="https://github.com/TheManticoreProject/Manticore/releases/tag/v1.0.9">Manticore v1.0.9&lt;/a> today. The release title is &lt;em>complete working SMBv1, NDR 2.0, and a bit of RPC&lt;/em>, and that is a fair summary of where the bulk of the work went. It is the largest release the library has shipped so far, with several hundred merged pull requests. The practical result is that Manticore can now drive an SMBv1 session and DCE/RPC calls end to end.&lt;/p>
&lt;p>This post walks through what changed, grouped by area.&lt;/p></description></item><item><title>Manticore v1.0.3: Parts of SMBv1 and minor fixes</title><link>https://themanticoreproject.com/blog/manticore-v1-0-3-smbv1-and-minor-fixes/</link><pubDate>Tue, 28 Oct 2025 16:12:47 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-0-3-smbv1-and-minor-fixes/</guid><description>&lt;p>Manticore is the Go library of offensive and defensive security primitives that powers the tools of The Manticore Project. It provides the building blocks (protocol structures, Active Directory abstractions, cryptographic helpers) that the individual tools rely on so that each tool does not have to reimplement the same plumbing.&lt;/p>
&lt;p>This release, v1.0.3, is a mix of new groundwork and small corrections. The headline is the start of SMB v1.0 support, but most of the work here is about tightening interfaces that already existed and adding the project governance documents that the repository was missing. None of these changes are large on their own; together they make the library a little more correct and a little easier to contribute to.&lt;/p></description></item></channel></rss>