Skip to content

Version 1.3.0

Latest

Choose a tag to compare

@aka-khalid aka-khalid released this 01 Nov 00:35
· 5 commits to main since this release

Timgr turns employee punch exports into a reviewed, period-based timesheet workbook. This is a signing release: the pipeline, the review screen and the saved workbook are unchanged, and every existing license keeps working. What changes is how a new signing key is trusted. The app now embeds one root public key, and that root can authorize a daily signing key without a new app build.

The app stays fully offline: no account, no server, no telemetry, and no network requests from the app itself.

Download

File Size SHA-256
Timgr_1.3.0_x64-setup.exe 5,456,463 bytes (5.20 MiB) AFF52823E20448064032910DF6793C433A04231F9DBF5BBF2BFAEE42302AD875

SHA256SUMS.txt is attached below. Check the download before running it:

Get-FileHash .\Timgr_1.3.0_x64-setup.exe -Algorithm SHA256

The result must match the hash above.

Requirements

  • Windows 10 (1809 or newer) or Windows 11, 64-bit.
  • About 200 MB free disk space after installation. The app itself is small; most of that is Microsoft's WebView2 runtime.
  • Internet only if WebView2 is missing on the machine. Windows 11 and any updated Windows 10 already have it, so a normal install never touches the network.
  • No administrator rights. The app installs for the current Windows user.

Install

  1. Run Timgr_1.3.0_x64-setup.exe.
  2. Windows SmartScreen may show "Windows protected your PC" because the installer is not code-signed. Choose More info, then Run anyway. Verify the SHA-256 first.
  3. If WebView2 is not present, the installer downloads and installs it silently. On an offline machine without WebView2, install the Evergreen Runtime first, then run this installer.
  4. The app installs for the current Windows user and adds a Start-menu shortcut. No admin prompt.

Upgrading from an earlier build (1.2.0, 1.1.0, 1.0.0) keeps everything: %APPDATA%\com.timgr.desktop (settings, drafts, export history, stored license) is untouched. A license that worked before still reads This device is licensed after the upgrade.

What's new in 1.3.0

  • A new signing key no longer needs a new app build. The app trusts one root key. The issuer uses that root once, with the root's code, to authorize a daily signing key. From then on the daily key signs licenses, and the app accepts them because the root says it may. The root code is used in that one step; it is never stored, never written to disk, and never shipped inside the app.

  • Delegated licenses are marked as such. A license signed by a daily key carries one small extra record, the delegation signed by the root. The License screen shows ISSUED UNDER with the root's name next to the key that signed. A license signed directly by the primary key is byte-for-byte what it always was, with no extra record.

    One limit, stated plainly: a delegated license verifies only on 1.3.0 or later. Older builds do not know about the root, so they reject it as an unsupported version. Install this build before asking for a license signed with a daily key. Directly signed licenses are unaffected and work everywhere.

  • The issuer shows the root and the delegation. The Signing key screen has a Root keys card, a Delegate a new key action, and a line naming the current delegation and the root that issued it. A delegated key is labelled as such, and its recovery code can still be shown, copied and moved to another PC like any other code.

  • The root code is refused as a daily code. Pasting it into Restore code says that it is the root, that a root never signs a license, and points to Delegate a new key. A delegated session is not disturbed by the attempt.

  • A damaged chain is named as such. If a license's delegation record was edited, the app says the license is damaged or was changed. If the record is missing, empty or repeated, it says the signing chain is not valid. A failed import never replaces the license already on the machine.

Verified on this build

Checked against the installed 1.3.0 app and the installed 1.1.0 issuer, not just in tests:

  • The installed issuer lists the ring of two keys with the primary in use, and shows the roots card with one root, timgr-fb35b7fb.
  • A key was delegated from the root: timgr-b5a47fa8, issued 2026-11-01 by timgr-fb35b7fb, and the issuer reported it as the current delegation.
  • A delegated license minted by that issuer is accepted by the installed app: This device is licensed, key timgr-b5a47fa8, ISSUED UNDER timgr-fb35b7fb.
  • Editing the delegation record inside that file: "This license is damaged or was changed." Repeating the record: "This license's signing chain is not valid." In both cases the license already stored on the machine stayed valid.
  • The same delegated file on an earlier 1.2.x build: "This license version is not supported.", both when it was already stored and when it was pasted. After reinstalling 1.3.0, the same file reads valid again.
  • The root code pasted into Restore code: refused, naming timgr-fb35b7fb and pointing to Delegate a new key. The delegated key stayed loaded.
  • A license signed by the primary key has no delegation record at all, and the installed app reads it as valid under timgr-652d4cf3.
  • npx tsc --noEmit clean; npx vitest run 253/253; both Rust crates green (54/54 app, 43/43 issuer); npm run release:check passes with the ring and the root; the 27 generated license vectors are reproduced identically.

Privacy

  • No account, no sign-in, no telemetry, no crash reporting.
  • The attendance file is read on your PC and never uploaded.
  • The app makes no network requests. The only network use anywhere is the installer fetching WebView2 when Windows is missing it.
  • Data lives in %APPDATA%\com.timgr.desktop (settings, drafts, export history, the installed license). Delete that folder to remove it.

Uninstall

Windows Settings > Apps > Timgr > Uninstall, or the Start-menu uninstaller. Drafts and history in %APPDATA%\com.timgr.desktop are kept; delete that folder to remove them too.

Notes

  • The installer is unsigned, so SmartScreen will warn. Code signing is a separate purchase and step.
  • The signing keys and the root code are not in this installer and not in the repository. They are held offline, in a password manager.
  • A root cannot be revoked or replaced without shipping a new app build. If the root code is lost, no new signing key can be delegated until a new root ships; the existing keys keep signing, so this limits new keys, not current licenses.
  • A leaked daily key cannot be revoked either: the fix is to delegate a new key, and licenses already signed by the old one stay valid, because trust is checked when a license is issued, not when it is used.
  • A no-WebView2 VM test is still recommended before wide distribution; this build was smoke-tested on a machine that already had WebView2.