search

bats3c / shad0w

A post exploitation framework designed to operate covertly on heavily monitored environments
https://blog.dylan.codes/shad0w/
MIT License
2.03k stars 323 forks source link

No active beacon #56

Closed merlin123h closed 4 years ago

merlin123h commented 4 years ago

Hi. I executed shad0w for first time with port number 430 . I got this error. Please guide me how to solve the problem. yyyyy

bblenard commented 4 years ago

Your screenshot doesn't really include an error. The No Active Beacon just means you haven't selected a beacon to interact with. From your screenshot it seems you just started the server and haven't had any beacons checkin yet. Notice how I get the same No Active Beacon Message when I initially start my server however once I execute a beacon on my test machine I get the initial checkin message and am able to interact and task the beacon.

Initial Server startup

no_beacons

Beacon Checkin

1_beacon

Also if you want to listen on port 430 you will have to publish the port via docker and instruct shad0w to listen on that port with -p 430 at the moment you are publishing port 430 however you are still listening on the containers 443. You could also probably --publish 430:443 to make it easy. Does that answer your questions?

bats3c commented 4 years ago

Nice, @bblenard covered everything you need to fix this issue.