Interest in cross-referencing / potential integration — adhammer (AD security toolkit)

Hi,

I'm the author of adhammer (https://github.com/icedracon/adhammer), an Active Directory security-assessment toolkit written in Rust. Rather than wrapping impacket or another Python stack, I ended up writing a from-scratch DCE/RPC / NTLM / SMB2 / Kerberos implementation to get a single static binary that runs on both Linux and Windows for authorized AD audit and red-team validation work (PingCastle-style scoring + BloodHound-style attack-path graphing + real PoC validation, e.g. actual DCSync/golden-ticket/pass-the-ticket artifacts, not just theoretical findings).

I think there could be real overlap between what I built and this crate. A few things I'd love to explore:
- Whether parts of my protocol stack (NTLM/Kerberos/SMB2 auth flows) could be split into standalone crates and cross-referenced with this project, so neither of us duplicates low-level protocol work
- Whether adhammer could consume sspi-rs directly for NTLM/Kerberos negotiation instead of my own implementation, if it covers the same ground
- General interest in comparing notes on Windows auth protocol edge cases — I hit a few gaps in public documentation while building this

Happy to share write-up/benchmarks:github.com/icedracon/adhammer Let me know if this is interesting or if I'm duplicating effort you've already solved better.

Zorayr

Start by reviewing sspi-rs's existing authentication coverage and comparing it with adhammer's NTLM, Kerberos, SMB2, and DCE/RPC stack. Determine whether a concrete integration or cross-reference is useful, and define the supported protocol scope and ownership before proposing implementation work.

Written by the indexing model from the issue text.