Closed mepher closed 6 years ago
Apparently commit https://github.com/EmpireProject/Empire/commit/2973bfe0c9abd11c3f346ef085b696ef770eb0ff broke some of the changes needed for DeathStar to run. I'll submit a pull request to straighten things out, in the meantime you can run
git revert 2973bfe0c9abd11c3f346ef085b696ef770eb0ff
in your cloned Empire directory to revert that commit and DeathStar should work fine.
Prologue:
* Starting Empire RESTful API on port: 1337
* RESTful API token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
But DeathStar doesn't wanna connect to API endpoint
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1137/python
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 661/sshd
tcp 0 0 0.0.0.0:1337 0.0.0.0:* LISTEN 1137/python
tcp6 0 0 :::22 :::* LISTEN 661/sshd
root@kali:# ./DeathStar.py --debug
[*] Powering up the Death Star
[-] Connection Error. Check Empire RESTful API
root@kali:# ./DeathStar.py -u empireadmin -p Password123 --url https://127.0.0.1:1337
[*] Powering up the Death Star
[-] Connection Error. Check Empire RESTful API
Solution: cd Empire/ git reset --hard 2677363e508c81834b27c31ae534a5474d37eda5 pip3 install pyopenssl
@byt3bl33d3r did you able to submit PR to empire?
@DanMcInerney your workaround didn't fix the problem for me
Any update on this ? running into same issue
Just submitted https://github.com/EmpireProject/Empire/pull/854 and updated DeathStar to reflect the API changes. Until the fix is merged you can use my fork of empire (https://github.com/byt3bl33d3r/Empire).
Thanks, @byt3bl33d3r for the update. That forked repo appears to have resolved the issue for me. Hopefully it gets merged sooner, rather than later!
The changes were just merged into the main Empire repo so this issue should be resolved.
Cheers
running the latest empire && deathstar everything goes well, until the agent calls in. then 'results' seems to be unpopulated. debug below: