Repository navigation
Kai 0.2.0
Kai moves to lmgw's device link: a key of its own, mutual TLS and no bearer. It needs lmgw 0.5.0 or later.
- Pairing over the device link. A pairing link now carries https URLs, lmgw's fingerprint and a one-time token. Kai makes its own key, enrols it over a connection pinned to that fingerprint, keeps the key in KWallet and connects with a certificate. Kai shows a code, lmgw's Devices card shows the same one, and you click Confirm there. Pasting or clicking the same link again after a failure enrols the same key.
- One link for everything. The feed, voice sessions, the tool link and the window's requests all use the same mutually authenticated client. Kai tries the link's URLs and then follows the address that answered. It takes the URL list and the dashboard address lmgw reports (Open in lmgw uses it), and the tooltip says when the certificate is due.
- Refusals in plain words. Kai says whether it waits for your Confirm, the certificate has lapsed or it must pair again. A stray TLS alert from another host on the address never makes Kai drop its pairing.
- Approvals follow the feed. The approval card shows calls that waited before Kai started, and a call you already decided does not come back.
- "Always allow" in a tool's confirmation sets that tool to allow for trusted callers.
- The tray's update check always shows its answer; new app and tray icons.
- Kai mobile, the Android client, is released alongside: https://github.com/lmgw-dev/kai-mobile
- MIT licence. Kai was FSL-1.1-MIT.
Upgrading: a pairing from Kai 0.1.0 used a bearer key, which lmgw 0.5.0 no longer accepts. Kai tells you to pair again; do it from the Devices card in lmgw, confirm the code, and Kai removes the old key from KWallet. Requirements are otherwise as for 0.1.0: KDE Plasma 6 on Wayland, PipeWire, KWallet, and lmgw 0.5.0 or later with its device listener on. Install the RPM from this release, or let Kai's update check offer it.