.deb is historical, .pkg. files weren't provided at the time of this package's creation, and since we only use the contents of the archive the format from upstream is unimportant. Also upstream no longer provides 32-bit Arch archives.
As for the expressvpn.xyz domain, that's where the archives were provided by expressvpn up until the latest version, which I've only just made aware of (apparently the new version alerts are broken again on Linux, and nobody flagged OOD). Package update coming shortly. Package security comes from the PGP signature checking. So long as you check the signature matches the PGP key used by upstream (defined in validpgpkeys), you can validate that the archives are official.
Pinned Comments
paintie commented on 2020-07-28 21:16 (UTC)
Info from expressvpn's site ...
wget https://www.expressvpn.com/expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc
gpg --import expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc
All installed fine; thank you very much for maintaining.
WorMzy commented on 2019-11-06 13:15 (UTC)
Looks like update notifications are working for the linux client now, but unfortunately the current version (2.3.2) thinks it's an older version (2.3.1 -- check
expressvpn --version
), so the update alert people get when they runexpressvpn status
may be a false positive.Please check what version is reported at https://www.expressvpn.com/latest (or https://www.expressvpn.com/support/troubleshooting/china-status/#linux as this sometimes gets updates listed sooner) before flagging the package as out-of-date.
WorMzy commented on 2019-01-11 11:38 (UTC) (edited on 2019-01-23 20:41 (UTC) by WorMzy)
Please note that, from v2.0.0, ExpressVPN will be providing signed Arch packages on their website (alongside the deb and rpm packages). I'll be continuing to update this package, but for those that find using the AUR cumbersome or just don't want to wait, please be aware of this option.
EDIT: packages were delayed for testing, but seem to be live as of 2019-01-23.