Outdated deb file and signature
parrotx-proton opened this issue · 2 comments
parrotx-proton commented
The deb file listed in documentation(https://protonvpn.com/support/linux-vpn-tool/) ie. https://protonvpn.com/download/protonvpn-stable-release_1.0.1-1_all.deb is outdated
$dpkg-deb -c ./protonvpn-stable-release_1.0.1-1_all.deb
drwxr-xr-x root/root 0 2021-05-25 15:00 ./
drwxr-xr-x root/root 0 2021-05-25 15:00 ./etc/
drwxr-xr-x root/root 0 2021-05-25 15:00 ./etc/apt/
drwxr-xr-x root/root 0 2021-05-25 15:00 ./etc/apt/sources.list.d/
-rw-r--r-- root/root 149 2021-05-25 15:00 ./etc/apt/sources.list.d/protonvpn-stable.list
drwxr-xr-x root/root 0 2021-05-25 15:00 ./usr/
drwxr-xr-x root/root 0 2021-05-25 15:00 ./usr/share/
drwxr-xr-x root/root 0 2021-05-25 15:00 ./usr/share/doc/
drwxr-xr-x root/root 0 2021-05-25 15:00 ./usr/share/doc/protonvpn-stable-release/
-rw-r--r-- root/root 246 2021-05-25 15:00 ./usr/share/doc/protonvpn-stable-release/changelog.Debian.gz
drwxr-xr-x root/root 0 2021-05-25 15:00 ./usr/share/keyrings/
-rw-r--r-- root/root 1765 2021-05-25 15:00 ./usr/share/keyrings/protonvpn-stable-archive-keyring.gpg
$cat /etc/apt/sources.list.d/protonvpn-stable.list
#
# ProtonVPN stable release
#
deb [signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
$sudo apt update
[sudo] password for parrot:
Err:1 https://repo.protonvpn.com/debian stable InRelease
403 Forbidden [IP: 104.26.8.21 443]
Hit:2 https://deb.parrot.sh/parrot rolling InRelease
Hit:3 https://deb.parrot.sh/parrot rolling-security InRelease
Reading package lists... Done
E: Failed to fetch https://repo.protonvpn.com/debian/dists/stable/InRelease 403 Forbidden [IP: 104.26.8.21 443]
E: The repository 'https://repo.protonvpn.com/debian stable InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.calexandru2018 commented
Hey @parrotx-proton
I'm not entirely sure what you mean by outdated, but judging by the output it seeks like the issue is that you're not able to access our repo. This though should've been fixed. Can you confirm this ?
parrotx-proton commented
Yes, its fixed now. I guess it was some wrong nginx rule on the server