Package monotime provides functions to access monotonic clock source.
2fa is a two-factor authentication agent. Usage: “2fa -add name” adds a new key to the 2fa keychain with the given name. It prints a prompt to standard error and reads a two-factor key from standard input. Two-factor keys are short case-insensitive strings of letters A-Z and digits 2-7. By default the new key generates time-based (TOTP) authentication codes; the -hotp flag makes the new key generate counter-based (HOTP) codes instead. By default the new key generates 6-digit codes; the -7 and -8 flags select 7- and 8-digit codes instead. “2fa -list” lists the names of all the keys in the keychain. “2fa name” prints a two-factor authentication code from the key with the given name. If “-clip” is specified, 2fa also copies the code to the system clipboard. With no arguments, 2fa prints two-factor authentication codes from all known time-based keys. The default time-based authentication codes are derived from a hash of the key and the current time, so it is important that the system clock have at least one-minute accuracy. The keychain is stored unencrypted in the text file $HOME/.2fa. During GitHub 2FA setup, at the “Scan this barcode with your app” step, click the “enter this text code instead” link. A window pops up showing “your two-factor secret,” a short string of letters and digits. Add it to 2fa under the name github, typing the secret at the prompt: Then whenever GitHub prompts for a 2FA code, run 2fa to obtain one: Or to type less:
Package clockwork contains a simple fake clock for Go.
Package analyzer checks workflow code for what breaks deterministic replay: goroutines, native channels and select, map iteration, the wall clock, randomness and sync primitives.
Command oracle serves envoyproxy/ratelimit's own ShouldRateLimit implementation, backed by Redis, with a clock and config that tests control.
Package pll keeps time for programs that must produce or consume things at a steady rate, or follow a clock other than their own.
Package dashcheck checks MPEG-DASH streams: the MPD, its segments, and for dynamic MPDs the timing against a synchronized wall clock.
Package testkit is the DMPF test instrument fixed by FND-09: one kit per layer of the pyramid (domainkit, serviceskit, providerkit, appkit, distkit), the golden-fixture loader with its three oracles reported apart (golden), the dependency rule as a fitness function over the production universe (fitness), the determinism primitives every kit shares (clock, ids, stable) and the testing.TB adapter that turns a Verdict into a test failure (tb).