Skip to content

Ensure Wireguard endpoint is valid before trying to use it#1024

Merged
rkervella merged 1 commit intoBishopFox:masterfrom
jamesgol:fix/931/wg
Dec 8, 2022
Merged

Ensure Wireguard endpoint is valid before trying to use it#1024
rkervella merged 1 commit intoBishopFox:masterfrom
jamesgol:fix/931/wg

Conversation

@jamesgol
Copy link
Contributor

@jamesgol jamesgol commented Dec 6, 2022

Fixes #931

@jamesgol jamesgol requested a review from a team December 6, 2022 03:01
@rkervella
Copy link
Member

That will work to fix the crash, I wanted to look deeper into why the netstack IP was empty in the first place. I believe this is a result of a previous refactor on the key exchange but I haven't taken the time to investigate.

@jamesgol
Copy link
Contributor Author

jamesgol commented Dec 6, 2022

That will work to fix the crash, I wanted to look deeper into why the netstack IP was empty in the first place. I believe this is a result of a previous refactor on the key exchange but I haven't taken the time to investigate.

It's not the most elegant but it works. I was stepping through the code and I think a bit more refactoring to separate the initial connect vs keyed connections is probably the proper fix but probably unnecessary unless something else pops up.

@rkervella rkervella merged commit 3b24870 into BishopFox:master Dec 8, 2022
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.

Sliver panics after failed Wireguard connection

2 participants