Right, to protect against delayed broadcasts this system requires that the receiver have a reasonable clock. If there's only one frequency of signed key distri

Right, to protect against delayed broadcasts this system requires that the receiver have a reasonable clock. If there's only one frequency of signed key distribution, then it has to be very high frequency, and the clocks can't suck too much. This can be ameliorated by having a second, lower frequency signed key distribution schedule (basically: every N) that can enlarge bad clock tolerance. Starting from scratch, with invalid time will make the device susceptible to attack, but if this is a rare event then it hardly matters because attacks should be detected by other devices ("herd immunity"?), but if there's a sufficiently low frequency key distribution schedule then a user can validate that the time the device got from Galileo seems right.