feat: add timezone-aware TOTP time travel
This commit is contained in:
+2
-1
@@ -4,10 +4,11 @@ A production-oriented, local-first browser workbench for OTP credentials and Web
|
||||
|
||||
Authentication material stays in the active tab. The application has no backend, telemetry, automatic network lookup, service worker, cookie, local-storage credential store, or IndexedDB database.
|
||||
|
||||
## Included in 0.1.0
|
||||
## Current source capabilities
|
||||
|
||||
- RFC 4226 HOTP and RFC 6238 TOTP generation and bounded diagnostic verification using SHA-1, SHA-256 or SHA-512, with exact 64-bit counters and preserved leading zeroes.
|
||||
- Strict `otpauth://` parsing/serialization, random secret generation, masked values, interoperability findings, live period display and a project-owned QR encoder.
|
||||
- Auditable TOTP time travel using positive/negative period offsets or a frozen local date/time in an explicit IANA timezone, including DST-gap rejection and repeated-time disambiguation.
|
||||
- RFC 6287 OCRA-1 suite parsing and computation for counter, numeric/alphanumeric/hex challenge, PIN/password hash, session and timestamp inputs. Official RFC interoperability vectors cover SHA-1, SHA-256 and SHA-512 paths.
|
||||
- Import of line-delimited provisioning URIs, Google Authenticator migration QR payloads, the documented CSV shape and RFC 6030 PSKC files containing plain secrets. Encrypted PSKC is rejected rather than guessed.
|
||||
- Explicit URI-list and CSV export with an unencrypted-secret warning.
|
||||
|
||||
Reference in New Issue
Block a user