Windows creates a new network connection/interface on every connect

[twocoolbeans]

Describe the Bug

Previously opened this as a feature request (https://github.com/orgs/fosrl/discussions/2772), but this a bug rather than a feature request.

When connecting to a Pangolin instance on Windows, either through OLM or the GUI client, a new virtual network connection and registry entry is created on every connection in the following locations:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\NetworkList\Signatures\Unmanaged
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

Below is a link to the pull request that another project used to solve the issue. Started looking into the solution, and it seems like the solution here will be similar:
netbirdio/netbird#2479

Environment

• OS Type & Version: Windows 11
• Pangolin Version: 0.9.0
• Gerbil Version: N/A
• Traefik Version: N/A
• Newt Version: N/A
• Olm Version: 1.4.4

To Reproduce

Install Pangolin on Windows. Connect to a network. Disconnect and reconnect. New entries will be visible below and the interface will be named something like olm2 or Pangolin2

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\NetworkList\Signatures\Unmanaged

and

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

Expected Behavior

Install Pangolin on Windows. Connect to a network. Disconnect and reconnect. The interface name should remain the same and new entries should not be created in the registry.

[AstralDestiny]

I hope I'm reading version 0.9.0 for pangolin version wrong.. if not update right now unless you're happy with having an RCE..

[twocoolbeans]

I hope I'm reading version 0.9.0 for pangolin version wrong.. if not update right now unless you're happy with having an RCE..

0.9.0 is the Pangolin Windows client version. I agree now that the server version was being asked for.