Package Details: private-internet-access-vpn 3.4-3

Git Clone URL: https://aur.archlinux.org/private-internet-access-vpn.git (read-only, click to copy)
Package Base: private-internet-access-vpn
Description: Installs VPN profiles for Private Internet Access Service
Upstream URL: https://www.privateinternetaccess.com/
Keywords: connman networkmanager openvpn python vpn
Licenses: GPL
Conflicts: xawtv
Submitter: flamusdiu
Maintainer: Auerhuhn
Last Packager: Auerhuhn
Votes: 86
Popularity: 0.000008
First Submitted: 2014-08-14 01:22 (UTC)
Last Updated: 2024-04-14 17:12 (UTC)

Pinned Comments

Auerhuhn commented on 2023-10-27 08:23 (UTC) (edited on 2023-10-27 08:23 (UTC) by Auerhuhn)

Note that this package provides only VPN profiles but not the vendor’s software.

The package version refers to the python-pia tool by @flamusdiu, which may lag behind the vendor’s own VPN software version.

Please do not flag this package out-of-date unless @flamusdiu releases a new stable python-pia version.

Thank you!

Latest Comments

« First ‹ Previous 1 .. 31 32 33 34 35 36 37 38 39 40 41 .. 48 Next › Last »

mindofthemad commented on 2016-05-30 02:39 (UTC)

The new update still has trouble connecting sha256. it authenticates the connection but i cant ping the network

flamusdiu commented on 2016-05-30 02:02 (UTC)

@kleshas: wth ... that's odd (and new too). I wonder if I broken something for running the configs directly with OpenVPN (which I do not do that often). Sorry about breaking it.

kleshas commented on 2016-05-30 01:59 (UTC)

This package broke for me since the update last week. I've been applying the patches that were released today, but I still get an error: $sudo openvpn /etc/openvpn/CA_Toronto.conf Options error: --up script fails with '/etc/openvpn/update-resolv-conf.sh': No such file or directory (and yes, there is no such file there)

flamusdiu commented on 2016-05-29 21:59 (UTC) (edited on 2016-05-29 22:32 (UTC) by flamusdiu)

@cryzed: there isn't a way to run 'pia -a' without root escalation because the login.conf file is read only by root and where both NM and CM store configuration files are also root only writes. * Users don't have to do an extra step after installation <<-- this can actually be done anyway. Problem would be if people wanted to customize it before they run "pia -a." * Users won't have to trust your script to not accidentally destroy their system (no root) <<-- it has to run as root as stated above. * If "pia -a" fails, the entire build fails, preventing a potentially misconfigured networking stack <<--I don't know how my script would destroy your network stack. VPN configs sure for some reason but not the whole network stack. As for the pacman hook, never though of adding one actually; so, I have no idea how I could decide against it in the first place. =\

cryzed commented on 2016-05-29 00:24 (UTC)

Another thing: What do you think about running "pia -a" (without root escalation) on the package before installing it, instead of having the user run the script manually? It's not like people are constantly switching between network management solutions (i.e. NetworkManager and ConnMan), so doing it during the installation would remove a few problems: * Users don't have to do an extra step after installation * Users won't have to trust your script to not accidentally destroy their system (no root) * If "pia -a" fails, the entire build fails, preventing a potentially misconfigured networking stack * Changes to the filesystem are tracked by the package manager (as they should be) Additonally, if you really want to preserve the ability to regenerate configuration files on-the-fly, you could probably just add pacman hooks that trigger for connman and networkmanager (un)installations. Is there a reason you decided against this?

cryzed commented on 2016-05-28 02:07 (UTC) (edited on 2016-05-28 02:41 (UTC) by cryzed)

The new version breaks for me, see: https://github.com/flamusdiu/python-pia/issues/6. After having removed the NetworkManager configuration files with "pia -r" and failing to regenerate them with "pia -a", the configuration files were predictably missing.

flamusdiu commented on 2016-05-27 22:19 (UTC)

Pushed new version. let me know if there are any odd issues. You can post on the github page for python-pia. Thanks!

flamusdiu commented on 2016-05-27 21:56 (UTC)

@cmc: I am confused. How does PIA conflict with Prey? Even doing a tree after building the package. I don't see any conflicts.

flamusdiu commented on 2016-05-24 19:49 (UTC)

I will try to do this week. I've been out of the country. @StudsWaller: yeah, I'll have to get it updated.

Svante commented on 2016-05-24 08:05 (UTC)

@flamusdiu When will you have time to update?

« First ‹ Previous 1 .. 31 32 33 34 35 36 37 38 39 40 41 .. 48 Next › Last »