Skip to content

Kiri 0.1.17

Choose a tag to compare

View all tags
@libracoder libracoder released this 03 Nov 22:18
· 27 commits to main since this release
v0.1.17
This tag was signed with the committer’s verified signature.
libracoder Precious Okwu
SSH Key Fingerprint: Kxk7E/Ge3AegCToKduek5bOkpbNN9425xcBnIKX5yhQ
Verified
Learn about vigilant mode.
77c2911
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fixed

  • Turning off automatic updates now sticks. On Mac, Windows and Linux, Settings showed Off, but the choice wasn't saved, so Kiri checked for updates again at the next launch. It's saved now.
  • Turning on crash reports sends only new crashes. Switching them on used to send every crash still waiting, including ones you'd answered Not now to. Kiri now sends only crashes from after you turned reports on. You can still send an older one yourself from its card.
  • Logs and reports take out more secrets. Passwords in URLs, Authorization values of any kind, PEM private keys, values after flags such as --password, GitHub, GitLab, Docker Hub and AWS access key tokens, and keys such as PGPASS, API-KEY and *_PRIVATE_KEY are now replaced with [redacted] before anything leaves your computer. It errs towards taking out too much: the whole user part of a URL goes, not only its password.
  • Windows: updates stay on HTTPS. Kiri no longer follows a redirect from the update feed down to plain HTTP, and release builds no longer accept a feed from a local file.
  • Crash reports never carry your Kiri Cloud account. A crash sent while you were signed in to Kiri Cloud went with your sign-in, so it named your GitHub account. Crashes now always go without it. A diagnostics report you send yourself still says it's from you, so we can reply, and the Send dialog says so.
  • Crash reports leave out your image and container names. The log lines a crash report carries named the images you pulled and the containers that stopped, including private registries. Those names are now taken out wherever they appear in the report.
  • Windows: reports take out your user name in every form. Your home folder was only blanked when written exactly as C:\Users\you. Now it also goes in lower case, with forward slashes, doubled inside JSON, as WSL's /mnt/c/Users/you, and as /home/you in the engine's log.
  • Still more secrets are redacted. password: … and key = … with spaces, Cookie and Set-Cookie headers, X-Api-Key, JWTs, Stripe, Slack, Anthropic, OpenAI, Google, npm and PyPI tokens, and email addresses. A secret written inside another value, such as env=[DB_PASSWORD=…, is no longer missed.
  • Settings says exactly what a crash report sends: the stack trace, the last 200 log lines, versions, the computer's model and a random ID for this install.

0.1.16 was tagged but never released; its fixes are in this release.

Thanks to @9trocode for the first four fixes, Kiri's first outside contribution.

Downloads for macOS, Windows and Linux: https://runkiri.com/releases/

Assets 18
Loading