Since equinox hosts any package, it's actually very difficult to check the PKGBUILD to ensure you're installing legit software, and not any random exe.
I would always cross-check the binary against https://dl.equinox.io/ngrok/ngrok-v3/stable/archive
(for me the easiest is just to open the developer tools for the website and ctrl-f find the identifier).
For example, the current PKGBUILD (as of 3.10.1) contains this line: source_x86_64=("https://bin.equinox.io/a/81d5kzodW8G/ngrok-v3-3.10.1-linux-amd64")
but I cannot find 81d5kzodW8G in the ngrok-v3 website link. Therefore, I have locally patched it by running these steps:
Edit the PKGBUILD (I removed all the other flavors besides x86_64 to make my life easier. Replace the source with source_x86_64=("https://bin.equinox.io/a/gzCri6c7dA3/ngrok-v3-3.10.1-linux-amd64.tar.gz")
Run makepkg -g
to generate the sha256 sums and replace those in the PKGBUILD as well.
Finally, fix the .SRCINFO with makepkg --printsrcinfo > .SRCINFO
@brenekh it would be really appreciated if you could convert your process to use the download files that are on this page: https://dl.equinox.io/ngrok/ngrok-v3/stable/archive so we could easily audit them. Thank you!
Just to add: I'm not accusing anyone of maliciousness here, just an abundance of caution.
Diffing the file in PKGBUILD (https://bin.equinox.io/a/81d5kzodW8G/ngrok-v3-3.10.1-linux-amd64) versus the one inside https://bin.equinox.io/a/gzCri6c7dA3/ngrok-v3-3.10.1-linux-amd64.tar.gz and they are the exact same.
Pinned Comments
brenekh commented on 2022-04-20 17:11 (UTC)
ngrok v3 introduces breaking changes.
Check https://ngrok.com/docs/guides/upgrade-v2-v3 for the upgrade instructions.
daurnimator commented on 2019-03-06 21:05 (UTC)
Note to self/future maintainers, this software only provides official downloads for an old release. The package itself then tries to update itself using 'equinox'. To find out the real download url, I use this script
get_download_info
:You need to call it with the different architectures: