Comment
The change only refreshes the SHA-256 checksums for the NordVPN Debian package downloads across architectures. The source URLs remain HTTPS and point to the vendor’s official repository, and there are no new build-time commands, scripts, or packaging behaviors introduced in this hunk. I don’t see evidence of added persistence, privilege escalation, or integrity bypass in the diff itself. Risk is low, though as with any binary package the trust boundary remains the upstream vendor release.
@@ -18,11 +18,11 @@ source_i686=("https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/n/nordvpn/no
source_armv7h=("https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/n/nordvpn/nordvpn_${pkgver//_/-}_armhf.deb")
source_aarch64=("https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/n/nordvpn/nordvpn_${pkgver//_/-}_arm64.deb")
source_armeabi=("https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/n/nordvpn/nordvpn_${pkgver//_/-}_armel.deb")
-sha256sums_x86_64=('34cdea72a75c9700c285b950ed2ec96acaeed4d607013a3abd18366731f8c334')
-sha256sums_i686=('c6e3908876941698a41287e01ca4327d9f2c0116469c2de072e3767ba551c5ae')
-sha256sums_armv7h=('34ee5e8ee89b22a1082b67253ca9eb61bcd4c158afb3a163b00c5b6679178c71')
-sha256sums_aarch64=('87fc3fbacd289fbf2242d52b62da363b7e799701504dd7a98013db63df372999')
-sha256sums_armeabi=('43caf6489ebc9d9f97d97be40312abfbfb7e07022aed76294830818cd993e1ca')
+sha256sums_x86_64=('57669d407215f34cd80b56d0b953dcd0ab8dcd3413ed18c646f666e0582e013a')
+sha256sums_i686=('2843b52f358f3b0eb20f2ffc8dfbb9937f2a4db11195d359cfe65c04a40b4ad8')
+sha256sums_armv7h=('515d4206c8803b27a72564612730f06ff5870ecd9385674142bc171c20045b8f')
+sha256sums_aarch64=('0a343574ec985def2d1b8ff9fde404568d95664f7e927655d11f4b01616e394e')
+sha256sums_armeabi=('960cc36b3753651a8e85afc13567dc8f5405acce0e7ec7a98f221bd411f0deb5')
package() {
bsdtar -O -xf *.deb data.tar.gz | bsdtar -C "${pkgdir}" -xJf -