Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/brave/brave-browser/issues/33726 below:

Windows should not install VPN services until VPN is purchased/enabled · Issue #33726 · brave/brave-browser · GitHub

Starting with product version 1.59.117 on Windows, WireGuard is used as the default for Brave VPN.

With product version 1.57.47, Brave will install a service Brave Vpn Wireguard Service if a user has admin privileges. This service is marked as Manual start and is not started. The binary is also installed on disk in the directory the the browser binaries are installed.

This change was introduced here:
brave/brave-core#18565

The pull request links to the devops issue where we compile the binary and also to the privacy/security review where this was vetted. Originally, this work was all behind a feature flag exposed via brave://flags.

There is also a Brave Vpn Service that is installed (also set to Manual start, not started) which has been there for a longer time. This service was added here:
brave/brave-core#15915

That change went live with Brave product version 1.50.114 on Windows. This service was added to provide an OS level way to stop leaking of DNS due to a Windows feature called Smart Multi-Homed Name Resolution and is only used when a customer has purchased VPN and the VPN is connected. More information about Smart Multi-Homed Name Resolution and why this service was created can be found here:
#25489

Here is a picture from services.msc courtesy of ghacks.net

These services will only be used when the person buys Brave VPN (via account.brave.com) and engages with the UI in the product.

On Windows only, there are two VPN related services (Brave Vpn Service and Brave Vpn Wireguard Service) registered with Windows when Brave is freshly installed. They can be viewed in services.msc. They are both set to Manual start and are not used until a person 1) uses Brave and 2) purchases Brave VPN and then 3) connects to Brave VPN.

At that point, a config (with the VPN details) is written to disk and the service is started.

These services are installed at install time - since the installer is already doing a UAC prompt (admin escalation). The ideal situation would be to move these services to be installed when VPN is first USED (post purchase) and not at install time.

As we solve this issue, here's what we plan to do

• Remove the service registrations during install (for Brave Vpn Service and Brave Vpn Wireguard Service). This will prevent new users from having the service installed.
• "Componentize" the binaries for these services, similar to Tor and IPFS. Those can be viewed in brave://components. There would be a new entry here like Brave Vpn Services (Windows).
  
• Update the VPN code to download/install the component at time of use
• Remove the service registrations during upgrade - so folks who have this service installed will have the service removed.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3