[Tool request] GhostPack (Work In Progress)

[osospeed]

https://github.com/GhostPack

Done:

• [x] ghostpack-safetykatz, PKGBUILD
• [x] ghostpack-sharpdump, PKGBUILD
• [x] ghostpack-sharpwmi, PKGBUILD

TODO:

• [ ] ghostpack-rubeus
• [ ] ghostpack-seatbelt, PKGBUILD Build FAILED. Program.cs(5,26): error CS0234: The type or namespace name 'Eventing' does not exist in the namespace 'System.Diagnostics' (are you missing an assembly reference?) [/tmp/ghostpack-seatbelt/src/Seatbelt/Seatbelt/Seatbelt.csproj]
• [ ] ghostpack-sharpdpapi
• [ ] ghostpack-sharproast, PKGBUILD Build FAILED. Program.cs(5,32): error CS0234: The type or namespace name 'AccountManagement' does not exist in the namespace 'System.DirectoryServices' (are you missing an assembly reference?) [/tmp/ghostpack-sharproast/src/SharpRoast/SharpRoast/SharpRoast.csproj]
• [ ] ghostpack-sharpup, PKGBUILD Build FAILED. Program.cs(6,26): error CS0234: The type or namespace name 'Eventing' does not exist in the namespace 'System.Diagnostics' (are you missing an assembly reference?) [/tmp/ghostpack-sharpup/src/SharpUp/SharpUp/SharpUp.csproj]

[noptrix]

nice @osospeed :) any news on this?

[osospeed]

• The initial idea was that we compile it on Linux, but as seen above this not so optimal.
• Second idea is to build it on windows using a CI server (e.g. Appveyor), and then take the binary Artifacts. In our case here, unfortunately my PR got rejected (https://github.com/GhostPack/SafetyKatz/pull/3). So in such cases what about making a Blackarch account on Appveyor which builds windows tools and push it to our repo here ? Any better idea ?

[vichhika]

Currently, I just saw this repository working on ghostpack binaries compiled. https://github.com/r3motecontrol/Ghostpack-CompiledBinaries

[D3vil0p3r]

https://github.com/BlackArch/blackarch/pull/4223

[D3vil0p3r]

This issue can be closed