Skip to content

touchenv 1.9.0

Choose a tag to compare

@ptrinh ptrinh released this 16 Nov 10:57
· 7 commits to main since this release

Approving a grant from afar, with a code from your phone. Away from the machine and driving an agent from your phone, you can now approve a timed grant with a six-digit code from an authenticator app, instead of Touch ID or Windows Hello:

touchenv totp setup --max-for 8h --max-uses 20     # once, at the machine, yourself
touchenv grant --intent "deploy" --totp 123456 --for 8h --uses 20 DEPLOY_KEY     # from afar: the agent runs this
  • Mac: for secrets synced through iCloud only (as --password): a secret kept on this Mac only stays behind Touch ID. Setup shows the key as a QR code in touchenv's own window, never in the terminal.
  • Windows (beta): for the keys you choose with touchenv totp allow NAME …. The touchenv service keeps the key behind the codes and a copy of each allowed key, encrypted to its own account, and checks every code itself; run touchenv service install again with this build. Setup shows the key as text to type into the app. Not yet tried on a real PC: it has passed the automated tests on Windows only.
  • A code works once, within the limits chosen at setup (12 hours and 100 uses unless you choose less). Wrong codes delay the next try; the fifth in a row locks codes until touchenv totp unlock at the machine. An AI assistant can't run totp setup.
  • A code doesn't say what it approves: the agent you give it to chooses the keys and the limits, within those of setup. Set the limits low and keep signing keys and admin tokens out of its reach. The README's new section Approving from afar compares it with a grant made before you leave; docs/security.md and docs/windows.md say what it gives up.

touchenv with no arguments, and touchenv help, now end with where the full instructions and updates are.

macOS and Windows (beta); the Windows exe is signed (SENPRINTS LLC).