| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
- Add local wireguard go import
- Activate DAITA and add `wgActivateDaita` and `wgReceiveEvent` FFI
- Implement `start_daita` on Wireguard-go tunnel type
- Mention DAITA in `wireguard-go-rs` description
- Do not compile `wireguard-go-rs` on Windows
- Handle DAITA closed on `nil` event
- Handle daita action timeouts in libwg
- Remove noisy log lines
- Remove `maybenot_on_action` callback
- Remove unused link to `../build/lib` for `talpid-wireguard`
- Bump the `wireguard-go` submodule to a signed release tag in Mullvad's
`wireguard-go` fork.
- Update path to `libwg/go.sum` in verification script
Also:
- Use u64 instead of *mut void as log context
- Make Tunnel::set_config take a &mut self
- Use dyn Error instead of i32s for wg errors
Co-authored-by: Joakim Hulthe <joakim@hulthe.net>
|
|
Fixes issues GO-2023-2402, GO-2022-0969, GO-2023-1495, GO-2023-1571,
GO-2023-1988, GO-2023-2102 and GO-2024-2687.
None of these issues affected our app (they were all about HTTP/2 or
other parts of golang that wireguard-go don't use)
|
|
We already use go 1.21 in our build containers and build servers.
So this does not change what version we actually use, only make go.mod
reflect reality
|
|
|
|
While Windows support was removed, wireguard-go still indirectly require wintun. Removing wintun will cause `go mod vendor` to fail which is what some package managers use for installation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
