kleb/kBackup
Watch
1
0
Fork
You've already forked kBackup
 0
Code Issues Pull requests Projects Releases 4 Packages Wiki Activity Actions
4 releases 4 tags
  • v1.2.0 206233f70f

    kBackup v1.2.0 Stable

    kleb released this 2026-08-09 19:58:25 +02:00 | 4 commits to main since this release

    kBackup v1.2.0

    kBackup v1.2.0 is a production-signed reliability and recovery release. The
    exact tagged source is
    206233f70f1e1b51ff5b9225cd7e18dddbbe830d.

    Highlights

    • Restore operations now hold repository read protection for their full
      lifetime and deeply verify image data before opening or erasing a target.
    • Rescue restores bind destructive operations to the originally selected
      physical-device identity and reject changed, unproven, or malformed sources
      before mutation.
    • File restores preflight complete trees, destination collisions, Windows name
      limits, metadata targets, symlinks, streams, and shared subtrees before
      publishing changes.
    • Prune now authenticates every live cached location before any sweep, repack,
      or maintenance-state mutation, preventing stale cache metadata from deleting
      live data.
    • Changed-block image capture now verifies every copied-forward block instead
      of treating a sample as proof. Backup verification IDs and image pipelines
      are disk-bounded and use persistent worker pools.
    • Local credentials, schedules, overlays, maintenance state, and run history
      now use crash-durable replacement semantics, including committed-error
      handling and directory synchronization.
    • Backend listings stream with bounded retry deduplication, write sessions
      avoid repeated pack tables, and large backup/index workflows use bounded
      memory and I/O.
    • New authenticated readiness and status reporting covers persistence,
      retries, repository operations, web/IPC readiness, and activity health.
      Restore metadata warnings retain bounded path/operation details without
      exposing provider errors or credentials.
    • Snapshot and tree discovery are paged and deterministic. Corrupt manifests
      are reported as unavailable without hiding healthy recovery points.
    • Image restore and extraction now expose disk/volume selectors and paged tree
      browsing in the API, web UI, and TUI. The TUI also gains maintenance actions,
      and dashboard active-run/24-hour metrics remain complete while history stays
      paged.
    • Web routes are split into lazy-loaded chunks, restore dialogs reset cleanly,
      SSE invalidation is more precise, and CLI/rescue argument handling fails
      closed.

    Repository and snapshot formats remain compatible; this release does not
    perform a destructive data migration.

    Signing And Trust

    kBackup uses self-managed release trust rather than a commercial public
    code-signing certificate. Authenticate this exact trust-manifest SHA-256
    through an independent channel before enrolling the bundled root:

    405fbb57e597845d2d0f85855bd8df9f5cfad82ec3e54fbdb11cc010fa9dd020

    Approved production identities:

    • Authenticode signer certificate SHA-256:
      8edce320469b986ac0ee934bd84b06c98612f6f7e0a8ce228c9a9718ae4960fe
    • RFC 3161 timestamp certificate SHA-256:
      2a19aedf8fa8f61e5851562c354e7d27d0029ad3292510aba8051801675bb3d0
    • OpenPGP package-signing subkey:
      D1ED1F306D446FB0F7A3C0BD2B3AA6B27E33386A
    • Cosign public key SHA-256:
      2cb49a5331a5d0fb14347469bf2f4063969069f462d52e3b6ea75451462e5a3d

    The complete public bundle is attached as
    kbackup-v1.2.0-public-trust.zip. No private signing material is included.

    Verification

    Start with BUNDLES-SHA256SUMS, then use the platform archive for the complete
    SBOM, provenance, checksum, and Sigstore material:

    sha256sum -c BUNDLES-SHA256SUMS
cosign verify-blob --key v1/cosign/cosign.pub \
  --bundle SHA256SUMS.linux-amd64.sigstore.json \
  SHA256SUMS.linux-amd64

    The DEB and RPM carry native OpenPGP package signatures. The Windows CLI,
    daemon, and installer carry SHA-256 Authenticode signatures with critical RFC
    3161 timestamps. Windows reports them as trusted only after deliberate
    enrollment of the self-managed root and publisher certificates.

    Key convenience-download SHA-256 values:

    kbackup-setup-v1.2.0-x64.exe
f0840b9d631df672e3755dba0bacc7be628603f33cff514737255ef56f874882

kbackup_1.2.0_amd64.deb
db2313fa31a7b2d99968428e4a0af4a763ac5d41007d9136f03135eab74d4f77

kbackup-1.2.0-1.x86_64.rpm
4a8b96994fa8b8f483abc9df3232dcfbe54342a935b601687981061dba4596d0

    The exact signed artifacts passed clean disposable acceptance on Windows 11
    Enterprise 25H2/NTFS and Debian 13/ext4. Acceptance covered pinned trust,
    offline installation, service lifecycle, backup, byte-for-byte restore, deep
    check, scrub, credential reopen after service restart and OS reboot, uninstall
    state retention, and reinstall/reopen. Two isolated unsigned builds on each
    platform also matched byte-for-byte across all release artifacts.

    The supported platform and repository boundaries remain those documented in
    docs/support.md.

    Downloads