Replies: 1 comment
|
Not GitHub staff, but as far as I know there is no documented guarantee. Hosted runners are Azure VMs that sync time via the Hyper-V host/chrony, and GitHub doesn't publish an SLA or offer an attested way to verify the clock bound during a job. So yes, treat the runner clock as untrusted for security decisions. If you need an authenticated time bound, get it from outside the runner: an RFC 3161 timestamp authority, Roughtime, or a signed timestamp from your own server. You can also check |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Actions Runner
Discussion Details
Hello GitHub Team,
We are preparing a security-gated workflow using a standard GitHub-hosted ubuntu-24.04 runner.
Before allowing execution, we need to establish whether GitHub guarantees a maximum absolute deviation of the runner’s system clock from actual UTC throughout a job lasting up to 15 minutes.
Our authorization mechanism requires a verified upper bound of 1,000,000 microseconds (1 second).
Could you please clarify:
We are looking for technical documentation or an authoritative answer, not typical measured accuracy.
Thank you.
All reactions