[GoDeskio]

What was broken

The repository was a crypto library plus a health-only API. There was no console to use: eg-console pointed at encryptoglyph-console:placeholder, and the running API image did not even load eg_crypto.

• FF1 was implemented from the NIST spec in this tree, and Shamir sharing was hand-rolled GF(256) arithmetic.
• v3 key-commitment checks returned before the AEAD open, so a bad commitment failed faster than a bad tag.
• eg_crypto did not export ReauthGate, so api/tests/test_reauth.py could not import it.
• OpenBao, Postgres, and restic are compose services only. Nothing in the process called them, and the old copy described them as if the console existed.

What this changes

• Console at / with a hero, flat neumorphic buttons, glass cards, a dark brass palette, a cursor-following glow, reduced-motion support, and a collapsible nav. Other product names appear only inside feature cards, and those cards link out.
• /v1 sidecar does real seal, open, rewrap, blind index, key create, fingerprint confirm, and shred. Session keys stay in process memory, are wiped on shred, and are never returned. Responses carry fingerprints.
• The assistant runs deterministic commands with no model. OLLAMA_BASE_URL may only pick an action id from sanitized text. The chat path rejects secrets and never echoes them. Plaintext goes to the seal form only.
• FF1 now uses the fpe crate (AES). Shamir now uses blahaj, the fixed fork of sharks (RUSTSEC-2024-0398). Commitment and AEAD checks both run. Known-answer tests cover RFC 5869 HKDF, RFC 4231 HMAC, RFC 9106 Argon2id, the NIST FF1 samples, and the checked-in v3 envelope vector.
• INTEGRATION.md plus sdk/python/encryptoglyph_client.py and sdk/js/encryptoglyph.js. VERSION is 0.2.0. scripts/encryptoglyph-update.py only accepts this repo's GitHub release tarball and does not execute it. .github/workflows/release.yml checks that a v* tag matches VERSION.
• Playwright covers the console flows in CI. Compose builds the real image for both eg-api and eg-console. /healthz is still status and build only, and docs, redoc, openapi, and swagger stay unserved.

Streaming backup framing is unchanged: it is the published STREAM construction over RustCrypto XChaCha20-Poly1305, and the existing stream tests still pin that wire format.

Screenshots

Verification

• cargo test --locked and cargo clippy --locked --all-targets -- -D warnings
• cargo deny check (advisories, bans, licenses, sources)
• ruff check api and pytest (61 passed)
• npx playwright test in e2e (2 passed)
• Docker is not installed in this environment, so the exposure container was not run here. CI runs compose config and the exposure probe.

  

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​blahaj@​0.7.0
	cargo/​fpe@​0.6.1
	npm/​@​playwright/​test@​1.56.1

View full report