<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cleanup on The Manticore Project</title><link>https://themanticoreproject.com/tags/cleanup/</link><description>Recent content in Cleanup 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/cleanup/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></channel></rss>