Requesting Feedback: SAMR-Enum – New SAMR Enumeration Tool for Kali Linux?

Hello Kali Developers,

I’m reaching out to get some initial feedback regarding a new tool I’ve developed called SAMR-Enum. This SAMR enumeration tool was developed as part of my Master’s thesis in cybersecurity and is available on GitHub here: GitHub - studylab1/SAMR-Enum-Lab

Before investing time in learning the full packaging process for Kali Linux (as I’m relatively new to it), I’d like to know if there’s genuine interest in including SAMR-Enum in the distribution. I’m aware there are other SAMR tools already present, so I’d appreciate your thoughts on whether this tool fills any unmet needs or offers significant improvements.

If there’s interest, I’ll prepare a proper source package following Kali’s packaging guidelines and submit it for review. Your early feedback is crucial so that I don’t invest time into packaging if it’s not a good fit.

Thank you for your time and feedback!

EnumD

1 Like

Yeah if you package it up we would likely accept it. We love already packaged tools.

Thank you for your response. I’ll proceed with preparing the package according to Kali’s packaging guidelines. I hope that once it’s ready, it can be included in the distribution. Should you need any further details or clarifications about the tool or its features, please let me know.

1 Like

The whole process is described here

I’ve been working on preparing the samr-enum tool for Kali inclusion. While following the official packaging workflow (gbp buildpackage --git-builder=sbuild), I’ve been fixing issues step by step — however, the build process is still stuck due to persistent environment/toolchain problems, despite several days of debugging.

To align with Kali packaging standards, I’ve moved the tool and relevant changes to a dedicated GitHub repository:

:link: GitHub - studylab1/samr-enum: Tool to enumerate SAMR data from Windows hosts

The debian/* files are fully prepared and can be shared as-is.

Would it be acceptable to submit just the debian/ directory for review, or is a fully successful build required before sharing with the team?

1 Like