<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bcrypt on The Manticore Project</title><link>https://themanticoreproject.com/tags/bcrypt/</link><description>Recent content in Bcrypt on The Manticore Project</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 12 Nov 2025 10:07:49 +0000</lastBuildDate><atom:link href="https://themanticoreproject.com/tags/bcrypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Manticore v1.0.8: KeyCredentialLink refactor and cleanup</title><link>https://themanticoreproject.com/blog/manticore-v1-0-8-keycredential-refactor/</link><pubDate>Wed, 12 Nov 2025 10:07:49 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-0-8-keycredential-refactor/</guid><description>&lt;p>Manticore is the Go library of offensive and defensive security primitives I maintain for The Manticore Project. It provides the building blocks (Windows structures, cryptography, LDAP and network plumbing) that the project&amp;rsquo;s tools rely on. Not every release adds a feature; some exist to clean up and tighten the existing code.&lt;/p>
&lt;p>v1.0.8 is one of those. There are no new capabilities here. Instead, I spent this release refactoring the KeyCredentialLink and CustomKeyInformation code, tidying up the LDAP &lt;code>DNWithBinary&lt;/code> type, tightening error handling, and removing debug output that should never have shipped. This kind of work does not change what the library does, but makes it easier and safer to build on.&lt;/p></description></item><item><title>Manticore v1.0.7: KeyCredential refactor and BCrypt ECC keys</title><link>https://themanticoreproject.com/blog/manticore-v1-0-7-keycredential-and-bcrypt-ecc/</link><pubDate>Tue, 11 Nov 2025 12:21:19 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-0-7-keycredential-and-bcrypt-ecc/</guid><description>&lt;p>Manticore is The Manticore Project&amp;rsquo;s Go library of offensive and defensive security primitives. It is the foundation that most of our tools build on, so each release tends to focus on making one or two of those primitives more correct and more pleasant to use. In v1.0.7 I focused on the &lt;code>keycredential&lt;/code> package: extending its cryptographic key support, tidying up its internal structure, and aligning one piece of its API with the naming conventions used across the rest of the library.&lt;/p></description></item><item><title>Manticore v1.0.6: Windows CNG/BCrypt structures</title><link>https://themanticoreproject.com/blog/manticore-v1-0-6-windows-cng-bcrypt-structs/</link><pubDate>Fri, 07 Nov 2025 09:07:33 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-0-6-windows-cng-bcrypt-structs/</guid><description>&lt;p>Manticore is the Go library that backs the offensive and defensive security tooling of The Manticore Project. It collects the low-level primitives those tools rely on: wire structures, cryptographic key formats, identifier types, and parsers for the binary blobs that Windows and Active Directory hand you. The goal is that a tool author never has to re-implement a security descriptor parser or a UUID generator from scratch.&lt;/p>
&lt;p>In this release, v1.0.6, I focused on two fronts. The first is breadth: new Windows CNG/BCrypt key structures and the remaining members of the UUID family. The second is consistency: a sweep across the codebase to align naming and parsing APIs so that everything behaves the same way.&lt;/p></description></item></channel></rss>