Closed ampf27 closed 1 year ago
This issue is closed because it does not meet our issue template. Please resubmit with the correct template.
Reopening. Thanks for providing a lot of detail. In the future, leave all the section headers, even if you leave them blank. The bot is sensitive like that.
This issue is closed because it does not meet our issue template. Please resubmit with the correct template.
Thank you for clarifying about how to post an issue and for reopening the issue too
On Tue, Apr 20, 2021 at 2:21 AM Vincent Rose @.***> wrote:
Reopening. Thanks for providing a lot of detail. In the future, leave all the section headers, even if you leave them blank. The bot is sensitive like that.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/BC-SECURITY/Starkiller/issues/64#issuecomment-822900119, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCXBXJLB6QGU37QUHS6EKTTJTJJFANCNFSM43GZ4YKA .
Sorry I have not had time to really dig into this yet, but people on our Discord with the same problem were able to solve it with these commands
sudo apt update && sudo apt -y full-upgrade
Empire Version
Starkiller Version 1.7
OS Information (Linux flavor, Python version)
Describe the bug
Empire and deathstar (I'm aware it's not yours but if you could help)
To Reproduce
I run the commands
and both are working, but when I open starkiller both close automaticaly and do not run while starkiller is open
I have installed starkiller through
apt install starkiller
this is what I get on empire when I run starkiller
zsh: segmentation fault powershell-empire --rest --username empireadmin --password password123
and this is what I get on deathstar when I run starkiller
Expected behavior
I was expecting to be able to access to the deathstar listener on starkiller
Screenshots N/A
Desktop (please complete the following information): N/A
Additional context N/A
What can be the reason for these errors?
Thank you in advance