Use CLOCK_BOOTTIME also for amd64's time.now() in Go runtime #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change was missing in the original patch causing issues with GoLang time functions on chromebooks after device wakes up from sleep and leading to failed connections.
After running below code on Chromebook after it was sleeping since boot
elapsed will have a difference between CLOCK_MONOTONIC and CLOCK_BOOTTIME which is the time device was sleeping since boot. It should be reproducible on any device with arm64 and where CLOCK_MONOTONIC and CLOCK_BOOTTIME can give different values. This behavior leads to incorrectly testing expiry for keypairs and consequently failed connections.
Issue seems to be reported here:
https://www.reddit.com/r/chromeos/comments/r2t1x4/chromeos_update_breaks_wireguard_android_vpn_apps/