Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sleep before shutting down beacon instead of after #875

Merged
merged 2 commits into from
Sep 15, 2022

Conversation

jamesgol
Copy link
Contributor

Details

When using a windows implant + wireguard it looks like the beacon registration message is never recieved by the server because the session is closed too quickly.

Fixes #670

When using a windows implant + wireguard it looks like the beacon registration message is never recieved by the server because the session is closed too quickly.

Fixes BishopFox#670
@jamesgol jamesgol requested a review from a team as a code owner September 15, 2022 01:59
@r00t0v3rr1d3
Copy link
Contributor

Hero status 🎉

Wireguard beacons could connect, but results of commands weren't making it back.

This is a bit hacky.  It works, but it would be better if there was a way to wait till everything has been transmitted.
@moloch-- moloch-- merged commit c1ac4dd into BishopFox:master Sep 15, 2022
@jamesgol jamesgol deleted the fix-wg-beacon-win branch September 20, 2022 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wireguard “beacon” Never Registers
3 participants