Skip to content

Ask Key 1.0.3

Choose a tag to compare

View all tags
@A1mAssist A1mAssist released this 21 Oct 17:59
· 13 commits to main since this release
v1.0.3
f251655

Ask Key 1.0.3

Windows Hello now unlocks Ask Key only when an Agent actually needs it, and commands an Agent runs can use OpenSSH again.

Unlocking

  • Ask Key starts silently. At login it stays in the tray without opening a window. When an Agent request arrives while the vault is locked, Ask Key brings its unlock screen to the front instead of leaving the request to fail quietly.
  • Windows Hello is asked once. After you unlock, read approvals inside the session window you chose in Settings (5, 15, 30 or 60 minutes) no longer ask again. A write approval still asks every time, because it hands an Agent plaintext or grants a lasting permission.
  • A locked request is never half-run. It fails closed with a vault_locked status that tells the Agent to retry the same operation ID after you unlock. --wait-for-approval keeps the command, its working directory and its environment in memory and resumes in the same process.
  • A single left click on the tray icon opens the window.

Fixes

  • OpenSSH works again. Commands started through Ask Key received a filtered environment without ProgramData, which made ssh.exe and its family exit with code 255 and no output. ssh, scp, sftp, ssh-keygen and ssh-keyscan all run again.
  • The background-start notification names the unlock method this vault actually has. It used to promise Windows Hello even when no Hello enrollment existed.
  • The post-update Agent-access notice is translated.
  • Settings has a switch for automatic update checks. Turning it off stops the background check; the manual button still works.

Upgrading from 1.0.2

Run AskKeySetup-1.0.3.exe over the existing install, or use Check for updates inside Ask Key. The install is in place: saved credentials are not touched.

Verify your download

Get-FileHash -Algorithm SHA256 .\AskKeySetup-1.0.3.exe

Compare with the matching line in AskKey-1.0.3.sha256.

Uninstalling keeps saved credentials in %APPDATA%\AskKey. This build is unsigned, so Windows SmartScreen will warn.

See the English README.

Ask Key 1.0.3

Windows Hello 现在只在 Agent 真正需要时才解锁，Agent 运行的命令也恢复支持 OpenSSH。

解锁

  • 开机静默启动。 登录后只留在托盘，不弹窗口。vault 锁定时如果有 Agent 请求进来，请旨会把解锁界面切到前台，而不是让请求悄悄失败。
  • Windows Hello 只问一次。 解锁后在设置里选定的会话时长内（5 / 15 / 30 / 60 分钟），读取类审批不再重复询问。写入类审批每次都会问，因为它会把明文交给 Agent 或授予长期权限。
  • 锁定时不会执行一半。 请求以 vault_locked 状态失败，并明确告诉 Agent 解锁后用同一个 operation_id 重试。--wait-for-approval 会把命令、工作目录和环境变量留在内存里，解锁后同一进程继续执行。
  • 左键单击托盘图标即可打开窗口。

修复

  • OpenSSH 恢复可用。 通过请旨启动的命令，其继承环境缺少 ProgramData，导致 ssh.exe 一族以 255 静默退出。ssh、scp、sftp、ssh-keygen、ssh-keyscan 均已正常。
  • 后台启动通知按这个 vault 实际有的方式说明。 以前即使没有绑定 Hello，也会提示用 Windows Hello。
  • 升级后的 Agent 访问提示已翻译。
  • 设置里新增「自动检查更新」开关。 关掉后不再后台检查，手动按钮仍然可用。

从 1.0.2 升级

直接运行 AskKeySetup-1.0.3.exe 覆盖安装，或在请旨里用检查更新。这是原地安装，不会动已保存的凭据。

校验下载

Get-FileHash -Algorithm SHA256 .\AskKeySetup-1.0.3.exe

与 AskKey-1.0.3.sha256 中对应的一行比对。

卸载不会删除 %APPDATA%\AskKey 中保存的凭据。当前构建未签名，Windows SmartScreen 会提示。

完整说明见 中文 README。

Assets 11
Loading