opened
bradfitz
username_0
We have a very old fork of winipcfg-go that we've made a few local changes to but they were never upstreamed, as upstream moved:

https://godoc.org/golang.zx2c4.com/wireguard/windows/tunnel/winipcfg

... and we never sent them there.

We should upstream our changes and switch to using the `golang.zx2c4.com/wireguard/windows` module.

/cc @username_1
windows: 
issue
created
alexbrainman
username_1
Also before we close this issue, we should

- disable or archive repo https://github.com/tailscale/winipcfg-go

- remove replace github.com/tailscale/winipcfg-go in winmin go.mod

- remove winipcfg-go submodule in winmin

Alex
comment
closed
bradfitz
username_0
issue
created
alexbrainman
username_1
I think we should also

- remove github.com/tailscale/winipcfg-go package from winmin go.mod
- remove github.com/tailscale/winipcfg-go from winmin submodule list
- mark github.com/tailscale/winipcfg-go repo as archived or read-only - or delete altogehter

Thank you.

Alex
comment
reopened
alexbrainman
username_1
We have a very old fork of winipcfg-go that we've made a few local changes to but they were never upstreamed, as upstream moved:

https://godoc.org/golang.zx2c4.com/wireguard/windows/tunnel/winipcfg

... and we never sent them there.

We should upstream our changes and switch to using the `golang.zx2c4.com/wireguard/windows` module.

/cc @username_1
windows: update winipcfg fork, upstream changes
issue
closed
bradfitz
username_0
issue