cloudflared-mirror/cmd/cloudflared/updater
Devin Carr 2484df1f81 TUN-8630: Check checksum of downloaded binary to compare to current for auto-updating
In the rare case that the updater downloads the same binary (validated via checksum)
we want to make sure that the updater does not attempt to upgrade and restart the cloudflared
process. The binaries are equivalent and this would provide no value.

However, we are covering this case because there was an errant deployment of cloudflared
that reported itself as an older version and was then stuck in an infinite loop
attempting to upgrade to the latest version which didn't exist. By making sure that
the binary is different ensures that the upgrade will be attempted and cloudflared
will be restarted to run the new version.

This change only affects cloudflared tunnels running with default settings or
`--no-autoupdate=false` which allows cloudflared to auto-update itself in-place. Most
distributions that handle package management at the operating system level are
not affected by this change.
2024-09-11 16:00:00 -07:00
..
check.go TUN-3989: Check in with Updater service in more situations and convey messages to user 2021-03-03 13:57:04 +00:00
service.go TUN-3989: Check in with Updater service in more situations and convey messages to user 2021-03-03 13:57:04 +00:00
update.go TUN-8630: Check checksum of downloaded binary to compare to current for auto-updating 2024-09-11 16:00:00 -07:00
update_test.go TUN-8630: Check checksum of downloaded binary to compare to current for auto-updating 2024-09-11 16:00:00 -07:00
workers_service.go TUN-8630: Check checksum of downloaded binary to compare to current for auto-updating 2024-09-11 16:00:00 -07:00
workers_service_test.go TUN-7584: Bump go 1.20.6 2023-07-26 13:52:40 -07:00
workers_update.go TUN-8630: Check checksum of downloaded binary to compare to current for auto-updating 2024-09-11 16:00:00 -07:00