UAPI socket for the sandboxed Wireguard app #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change makes it possible to configure tunnels created by the App Store Wireguard UI using
wg
andwgctrl-go
.It's an implementation of this suggestion: WireGuard/wgctrl-go#96 (comment)
Because the app is sandboxed, you cannot create the socket in its usual location (
/var/run/wireguard
).It should be possible to configure an exception for the path but in practice it only works with regular files and not Unix domain sockets. That's why I create the socket inside the app's sandbox folder instead (
~/Library/Containers/com.wireguard.macos.network-extension/Data
). There's no problem connecting to that socket from outside as the command-line tooling is typically not sandboxed itself.I'm also submitting pull requests to modify
wireguard-go
,wgctrl-go
andwireguard-tools
to work with this alternative path.WireGuard/wireguard-go#89
WireGuard/wgctrl-go#143
WireGuard/wireguard-tools#21