v0.1.9

Changed

• Visual Studio solution versioned with the repository (Kubuno.Keestore.slnx, generated by vskubuno, the naming of
  every Kubuno repository): the server is the project Kubuno.Keestore.Server, the frontend Kubuno.Keestore.Web, in
  the solution folders Server, Libraries and Frontend, with the shared launch profile "Keestore (Kubuno Core + browser)".
  The crate and npm names do not change.

Added

• Keestore runs on MySQL/MariaDB and SQLite as well as PostgreSQL, chosen at
  run time. One build carries the three engines; the server picks one from
  its configuration at start-up. Everything a user does — upload, download,
  version check, delete — behaves identically on the three.

Changed

• Events no longer depend on a PostgreSQL-specific notification. They are
  announced over the core's internal interface instead, the path the other
  modules already use. Nothing changes for anyone using the module, and an
  event is no longer lost when a subscriber happens to be restarting.
• The vault's identifier is now generated by the module rather than by the
  database. Existing vaults keep theirs; this is what lets the module read a
  freshly saved vault back on an engine that cannot return it in one go.
• The write path moved out of the request handler into the vault service,
  where it is covered by tests that run against a real server of each of the
  three engines.

Security

• The signed-in user is now taken from the core's signed identity token only. The module used to trust the
  plain X-Kubuno-User-Id / -Role / -Email headers, so any process able to reach its local port could
  act as any user, administrators included. It now accepts a request only with a valid X-Kubuno-Auth token
  signed by the core with this module's own secret, for this module, and not expired (kubuno-modauth); the
  plain headers are ignored. With no internal secret configured, every user request is refused. An unused, non-constant-time IPC guard was removed (the module has no IPC route).

• Security fixes from the shared database layer (kubuno-db 0.9.0). The
  database password can no longer appear in a log through the debug output of
  the database settings.

• Database driver updated past an unfixable advisory. The previous line
  pulled in an RSA implementation vulnerable to a timing side-channel
  (RUSTSEC-2023-0071) for which no fix will ever exist. The new line does not
  depend on it at all, and it refuses any SQL string built at run time unless it
  has been audited — the queries here were checked and marked.

• Input validation library updated. The version in use carried
  RUSTSEC-2024-0421 through its domain-name parser, which accepted Punycode
  labels that decode to plain ASCII — a mismatch an attacker can use to make two
  different names look like one.

Fixed

• Database migrations keep the same checksum on every OS. The repository now
  pins line endings to LF (.gitattributes), so a checkout on Windows no longer
  turns SQL migrations, scripts, manifests or sources into CRLF. A database
  migrated by a Linux build is therefore no longer refused by a Windows or macOS
  build of the same version because its migration checksums differ.

v0.1.8

Security

• HTTP/2 layer updated to a patched release. h2 moves from 0.4.15 to
  0.4.19, closing a denial of service through unbounded empty DATA frames
  (RUSTSEC-2026-0258).
• Error library updated to a patched release. anyhow moves from 1.0.103
  to 1.0.104, closing an unsoundness in Error::downcast_mut()
  (RUSTSEC-2026-0190).
• TLS library updated to a patched release. The pinned rustls carried
  RUSTSEC-2026-0285 (medium). Every outbound HTTPS connection goes through it.

v0.1.7

Changed

• This module now installs as a Kubuno package (.kbpkg) only. Its system
  packages (Debian/RPM and the Windows and macOS installers) are no longer
  built: the module is distributed as one .kbpkg per platform (Linux, Windows,
  macOS) that the Kubuno server installs itself — from the admin console, or
  offline with kubuno modules:install <file>.kbpkg.

• Dates are formatted by the platform now, not by a library. date-fns is
  gone from this module: the shared SDK exposes helpers built on Intl, which is
  localised for every language we ship and needs no locale bundle loaded. Call
  sites say what a date is FOR — formatDate(d, 'date') — and the platform
  decides how to write it, so a reader in Japanese no longer gets a French
  layout. Machine formats (keys, <input type="date"> values) go through
  toISODate and friends, built from local calendar fields so the day cannot
  shift near midnight.

• The README now opens with the module's logo. The public README on
  GitHub now shows the module's designer logo (the same PNG shown as the
  browser tab icon and in the applications menu) at the top of the page — the
  repository landing now matches the icon a signed-in user sees inside the
  platform. The image ships in-repo, under .github/logo.png, so it renders
  even when the repo is browsed offline.

• New Keestore logo — a violet hexagon holding a white key, used as the
  browser-tab icon and in the applications menu. It is now raster (PNG)
  designer artwork.

Fixed

• A withdrawn dependency is no longer used. A crate deep in the tree
  (spin 0.9.8, pulled in through the HTTP stack) was yanked by its authors.
  No vulnerability was announced, but a withdrawn crate has no business in a
  release; the lockfile now takes the version that replaced it.
• The package could not be built where zip is absent. The Windows job of
  the continuous integration has no zip, so the Windows package was simply lost
  the first time it was attempted — a script failure, not a build failure. The
  builder now falls back to 7-Zip, then to PowerShell.

Added

• This module now ships a .kbpkg — the single package format a Kubuno
  server installs by itself, the same file on Linux, Windows and macOS. It
  carries the same binary, interface and manifest as the system packages,
  arranged the way the server expects to find a module on disk, plus a
  SHA256SUMS so a copy carried offline can be checked without the catalogue.
  Nothing changes for existing installations: the .deb, .rpm, .exe and
  .pkg are still published, and a catalogue that sees both simply prefers the
  new one. It is also the only format the server can unpack without an external
  tool, which is what makes one-click installation possible away from
  Debian-like systems.

Fixed

• A built package could be thrown away instead of published. The job that
  attaches a package to the release waited ten minutes for another workflow to
  create that release, then gave up with "release never appeared — build.yml
  likely failed". The diagnosis was wrong: on a repository whose .deb takes
  longer than ten minutes to build, the release simply did not exist yet, and a
  package that had built perfectly was discarded. Four modules reached v0.1.6
  with packages missing for some systems because of it. The job now creates the
  release itself when it is missing, so it no longer depends on another workflow
  finishing first.

Added

• Security policy and CI quality gate. A SECURITY.md documents how to
  report vulnerabilities, and a CI workflow enforces clippy -D warnings, a
  dependency-vulnerability audit (cargo audit) and the frontend typecheck/tests.

v0.1.6

Changed

• Theme tokens: two colours for navigation labels (--color-text-nav,
  --color-text-nav-active). Every module carries the same token sheet, so the
  values must match across them — whichever bundle loads last would otherwise
  win. No visible change inside this module.

Changed

• Default application background token aligned with the core (--body-bg #f8fafd). Only
  visible when the module runs standalone: inside the shell the active theme sets it.

v0.1.5

kubuno-keestore v0.1.5