Windows Support
phin3has opened this issue · comments
Brandon E. commented
It would be wicked to see some Windows love.
After installing requests, I get an initial traceback:
C:\Tools\clusterd>python clusterd.py
←[32m
clusterd/0.3.1 - clustered attack toolkit←[0m
←[33m[Supporting 6 platforms]←[0m
Traceback (most recent call last):
File "clusterd.py", line 108, in <module>
options = parse(sys.argv[1:])
File "C:\Tools\clusterd/src/core/parse_cmd.py", line 92, in parse
group = build_platform_flags(platform, group)
File "C:\Tools\clusterd/src/core/auxengine.py", line 65, in build_platform_flags
mod = auxiliary[0].find_module(auxiliary[1]).load_module(auxiliary[1])
File "C:\Python27\lib\pkgutil.py", line 246, in load_module
mod = imp.load_module(fullname, self.file, self.filename, self.etc)
File "C:\Tools\clusterd\src\platform\jboss\auxiliary\smb_hashes.py", line 8, in <module>
from os import getuid
ImportError: cannot import name getuid
bryan alexander commented
There are some platform-specific things that need to be extrapolated out. Off the top of my head:
- Permission check functions on SMB modules
- Manually shelling out to move stuff around - should switch to
shutil
- Output coloring won't work on Windows
bryan alexander commented
I've got this mostly working, but I think I'd have to castrate clusterd too much to make this a viable platform. In its current state it will perform basic scanning, but will choke on payload generation, auto-updating, etc. I'm going to close this as WONTFIX for now, but will remain cognizant of the platform.