View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007648||Kali Linux||[All Projects] New Tool Requests||public||2022-03-30 15:30||2022-04-29 14:03|
|Target Version||Fixed in Version|
|Summary||0007648: SMBeagle - SMB share auditing tool|
|Description||- [Name] - SMBeagle|
- [Version] - 2.1.0
- [Homepage] - https://github.com/punk-security/SMBeagle
- [Package] - https://gitlab.com/jw-barker/SMBeagle-2.1.0
- [Author] - Punk Security Limited
- [License] - Apache License 2.0
- [Description] - SMBeagle is an (SMB) fileshare auditing tool that hunts out all files it can see in the network and reports if the file can be read and/or written. All these findings are streamed out to either a CSV file or an elasticsearch host, or both!?
- [Dependencies] - None
- [Similar tools] - ShareAudit
- [Activity] - In active development, last release this month
- [How to use] - smbeagle --help
- [Packaged] No*
We struggled during the packaging process - we managed to get the .deb package to build, but the binary inside ended up corrupted. We have pretty much zero experience with packaging for Debian so hopefully it won't be too much effort to finish it off.
|Missed this out in the original ticket - we have our releases on github. Latest release is here: https://github.com/punk-security/SMBeagle/releases/tag/2.1.0|
I see that this has been unassigned. Is there anything else that we can do on our end?
We tried following the kali guides on publishing deb packages but ended up with a smaller package than expected and the resulting binary when installed appeared to be corrupted.
If anyone could give us any pointers to speed up the process then that would be great.
|2022-03-30 15:30||brandonatpunk||New Issue|
|2022-03-30 15:56||steev||Assigned To||=> g0tmi1k|
|2022-03-30 15:56||steev||Status||new => assigned|
|2022-03-30 15:59||brandonatpunk||Note Added: 0015980|
|2022-04-29 13:08||g0tmi1k||Assigned To||g0tmi1k =>|
|2022-04-29 14:03||brandonatpunk||Note Added: 0016092|