This is the desktop client for the Private Internet Access VPN service. It consists of an unprivileged thin GUI client (the "client") and a privileged background service/daemon (the "daemon"). The daemon runs a single instance on the machine and is responsible for not only network configuration but also settings and account handling, talking to PIA servers as necessary. The client meanwhile runs in each active user's desktop and consists almost entirely of presentation logic. No matter how many users are active on a machine, they control the same single VPN instance and share a single PIA account.

The project uses Qt 5 for cross-platform development, both in the client and daemon. The client GUI is based on Qt Quick, which uses declarative markup language and JavaScript and offers hardware accelerated rendering when available. Qt and Qt Quick tend to be more memory and CPU efficient compared to web-based UI frameworks like Electron or NW.js.

The client is intended to be built on the target platform; Windows builds are built on Windows, macOS builds on macOS, and Linux builds on Ubuntu.

The entire product is built using rake, using the supporting framework in the rake/ directory.

Dependencies such as OpenVPN and the Windows TAP driver are included as precompiled binaries under the deps directory in this project for convenience. To recompile any of these, please refer to their corresponding directories and/or repositories for build instructions.

• On Windows:
  • Git 1.8.2 or later with Git LFS installed
  • Qt 5.15 or later (open source edition)
    • Install CMake (under development tools) to use this project in Qt Creator
  • Visual Studio Community 2019 or Build Tools for Visual Studio 2019
    • Requires VS 16.7 or later
    • The Windows SDK must be at least 10.0.17763.0
    • Install the "Windows 8.1 SDK and UCRT SDK" to get the UCRT redistributable DLLs for 7/8/8.1
  • Debugger: Install Debugging Tools from the Windows 10 SDK
    • The VS installer doesn't include the Console Debugger (CDB), which is needed to debug in Qt Creator. More info: Setting Up Debugger
  • Ruby - includes Rake
  • 7-zip
• On macOS:
  • Git 1.8.2 or later with Git LFS installed
  • Qt 5.15 or later (open source edition)
    • Install CMake (under development tools) to use this project in Qt Creator
  • Mojave or newer
  • Up-to-date version of Xcode
  • Ruby, can be installed using Homebrew with brew install ruby
• On Linux:
  • Debian 9 (Stretch) or newer
    • Supported architectures: x86_64, armhf, arm64
  • Git 1.8.2 or later with Git LFS installed
  • Qt 5.15 or later
    • PIA's build of Qt is recommended: desktop-dep-build releases
    • If you want Qt Creator, also install Qt from qt.io
  • To build natively on the host, install the following development packages:
    • build-essential
    • rake
    • clang (or specific version, clang-7 recommended on Debian Stretch)
    • mesa-common-dev
    • libnl-3-dev (PIA can run without the library installed, but the headers are needed to build)
    • libnl-route-3-dev
    • libnl-genl-3-dev
    • git (needed even in chroot build environment, to determine commit info for version)
  • To build releasable artifacts (always built under Debian 9, and optionally including arm64/armhf cross builds), set up Debian 9 chroots - see "Building for Distribution" - "Linux" below

Before cloning the Git repository, first make sure Git LFS is installed and initialized:

> git lfs version
git-lfs/2.3.4 (GitHub; windows amd64; go 1.8.3; git d2f6752f)

> git lfs install
Updated git hooks.
Git LFS initialized.

After this, cloning the repository normally should also fetch the precompiled binaries:

> git clone https://github.com/pia-foss/desktop.git
...
Filtering content: 100% (24/24), 17.13 MiB | 1.89 MiB/s, done.

The following targets can be passed to rake. The default target is stage, which stages the built client, daemon, and dependencies for local testing (but does not build installers, tests, etc.)

👉 In 2.3.0 and earlier, PIA used a qbs-based build system, along with postprocessing to generate final installer artifacts in the various platform build scripts. This is now all done using Rake, the qbs build system has been removed.

The build system has several properties that can be configured, either in the environment or by passing the appropriate variables to rake.

These are implemented in rake/build.rb. The output directory name includes the current brand, variant, and architecture.

Some additional environment variables can be configured:

To open the project in Qt Creator, open CMakeLists.txt as a project. This CMake script defines targets for Qt Creator and hooks them up to the appropriate rake tasks, which allows Qt Creator to build, run, and debug targets.

Some specific configuration changes are useful in Qt Creator:

The file locator (Ctrl+K / Cmd+K) can only locate files referenced by targets by default. The CMake script allows it to find most C++ source, but it can't find QML source or other ancillary files. Enable the "Files in All Project Directories" filter by default:

1. Open Qt Creator's Preferences
2. Go to Environment > Locator
3. Next to "Files in All Project Directories", check the box for "Default"
4. Select "Files in All Project Directoreis" and click "Edit..."
5. Add the exclusion patterns "/out/" and "/node_modules" (to exclude build outputs and modules installed for ancillary JS utility scripts)

This is a good idea anyway because it also allows you to find files not used by a target, like Rakefile, .gitignore, build scripts, etc.

Qt Creator's default target is 'all', which is hooked up to rake's default - the staged installation only. You can also set Qt Creator's default to really build everything (including running tests) or to build the current executable (useful to build specific tests, but not needed to debug them from Qt Creator).

1. Go to the Projects page
2. Select "Build" under current kit"
3. Under "Build Steps", expand the CMake build step
4. Select a different target instead of "all":
   • "rake-all" will build everything, including running unit tests
   • "Current executable" will build the current target you have selected in Qt Creator - for client/cli/daemon this builds the staging area, but for integtest or unit tests it will build the test instead

Qt Creator will still ask to select a kit, which includes a Qt version, compiler, etc. This has no effect on the build output - the Rake scripts find Qt and the compiler on their own, which allows them to be run with no prior setup. Select the same Qt version and compiler in Qt Creator that the rake script uses, so Qt Creator's code model will work.

On Windows, Qt Creator will run rake in an environment set up using vcvarsall.bat, which is not necessary (since the rake scripts run vcvarsall.bat automatically) but may cause stale MSVC variables to remain in the build environment if you update MSVC. Just do a clean and re-run cmake from Qt Creator, and the environment should be reset.

rake artifacts (or rake all) produces the final artifacts for distribution, including signing if code signing details are provided. Code signing environment variables are defined below.

Build scripts in the scripts directory are also provided that clean, then build for all architectures supported on a given platform.

Set environment variables:

Then call scripts/build-windows.bat

Set environment variables:

Call scripts/build-macos.sh

A certificate is required for the Mac build to be installable (even for local builds), see below to generate a self-signed certificate for local use. Unsigned builds can be manually installed by running the install script with sudo.

If you have not already done so, set up Debian 9 build chroots. This requires debootstrap and schroot.

$ ./scripts/chroot/setup.sh # native x86_64 build environment
$ ./scripts/chroot/setup.sh --cross-target arm64 # arm64 cross build environment
$ ./scripts/chroot/setup.sh --cross-target armhf # armhf cross build environment

Set environment variables:

Then call scripts/build-linux.sh.

Each platform requires additional installation steps in order for the client to be usable (e.g. the Windows TAP adapter needs to be installed). The easiest way to perform these steps is to build and run an installer, after which you can stop and run individual executables in a debugger instead.

To debug your own daemon, the installed daemon must first be stopped:

• Windows: Run services.msc and stop the Private Internet Access Service
• macOS: Run sudo launchctl unload /Library/LaunchDaemons/com.privateinternetaccess.vpn.plist
• Linux: Run sudo systemctl stop piavpn

The daemon must run as root. Consult your IDE/debugger documentation for how to safely run the debugger target as root.

Installation on Mac uses SMJobBless to install a privileged helper that does the installation.

Mac OS requires the app to be signed in order to install and use the helper. If the app is not signed, it will not be able to install or uninstall itself (you can still install or uninstall manually by running the install script with sudo.)

PIA_CODESIGN_CERT must be set to the full common name of the certificate to sign with. (codesign allows a partial match, but the full CN is needed for various Info.plist files.)

To test installation, you can generate a self-signed certificate and sign with that.

• Open Keychain Access
• Create a new keychain
  1. Right-click in the Keychains pane and select "New Keychain..."
  2. Give it a name (such as "PIA codesign") and password
• Generate a self-signed code signing certificate
  1. Select your new keychain
  2. In the menu bar, select Keychain Access > Certificate Assistant > Create a Certificate...
  3. Enter a name, such as "PIA codesign", it does not have to match the keychain name
  4. Keep the default identity type "Self Signed Root"
  5. Change the certificate type to "Code Signing"
  6. Click Create, then Continue
• Optional - disable "lock after inactivity" for your keychain
  1. Right-click on the keychain and select "Change Settings for Keychain"
  2. Turn off locking options as desired
• Use the certificate to sign your PIA build
  • Qt Creator:
    1. Select Projects on the left sidebar, and go to the build settings for your current kit
    2. Expand "Build Environment"
    3. Add a new variable named PIA_CODESIGN_CERT, and set the value to the common name for your certificate
  • Manual builds with build-macos.sh
    1. Just set PIA_CODESIGN_CERT to the common name you gave the certificate when building

By contributing to this project you are agreeing to the terms stated in the Contributor License Agreement. For more details please see our Contribution Guidelines or CONTRIBUTING.

Unless otherwise noted, original source code is licensed under the GPLv3. See LICENSE for more information.