ReaperOfVeriod/trixy-linux-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Linux keyring storage boundary

Browse Source
This commit is contained in:
ReaperOfVeriod
2026-10-25 05:43:45 +01:00
parent d7dad3021f
commit 761ff5305d
428 changed files with 1170 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -3
View File
@@ -4,9 +4,10 @@ This directory is the home of the standalone Linux client repository.
The current development shell connects to the server readiness endpoint and
provides an administrator login gate. The browser/dev client keeps its bearer
session in memory only; the native AppImage integration must replace that
temporary behavior with the Linux kernel keyring before persistent client
authentication is considered complete.
session in memory only. The `native/` crate defines the AppImage storage
boundary: `settings.json` contains only the server address and username, while
the session credential is stored in the Linux kernel keyring with no plaintext
fallback.
The client is a Svelte-based control surface distributed as an x86-64 AppImage. It communicates with `trixie-server` through the documented versioned HTTP and authenticated WebSocket interfaces.