-
kBackup v1.2.0 Stable
released this
2026-08-09 19:58:25 +02:00 | 4 commits to main since this releasekBackup 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:405fbb57e597845d2d0f85855bd8df9f5cfad82ec3e54fbdb11cc010fa9dd020Approved 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-amd64The 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 4a8b96994fa8b8f483abc9df3232dcfbe54342a935b601687981061dba4596d0The 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
- Restore operations now hold repository read protection for their full
-
v1.1.1 Stable
released this
2026-07-27 21:40:10 +02:00 | 53 commits to main since this releasekBackup v1.1.1
This production-signed release contains the redesigned embedded web interface.
The exact tagged source is
116b57e3d2e0e798a36ed0ec10d782a8c6944f9d.Changelog
- Redesigned the dashboard, repositories, jobs, authentication, and setup
experiences for clearer operational use. - Added light and dark themes with a persistent theme control.
- Added consistent state indicators, page structure, tables, dialogs, and
responsive navigation. - Added the new kBackup favicon and refreshed visual styling throughout the web
interface. - Kept the existing owner-token authentication and TUI-generated one-time setup
link behavior. - Rebuilt and embedded the new web UI in every shipped daemon and package.
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 installing the bundled root:405fbb57e597845d2d0f85855bd8df9f5cfad82ec3e54fbdb11cc010fa9dd020Approved production identities:
- Authenticode signer certificate SHA-256:
8edce320469b986ac0ee934bd84b06c98612f6f7e0a8ce228c9a9718ae4960fe - RFC 3161 timestamp certificate SHA-256:
2a19aedf8fa8f61e5851562c354e7d27d0029ad3292510aba8051801675bb3d0 - OpenPGP signing subkey:
D1ED1F306D446FB0F7A3C0BD2B3AA6B27E33386A - Cosign public key SHA-256:
2cb49a5331a5d0fb14347469bf2f4063969069f462d52e3b6ea75451462e5a3d
The complete public bundle is attached as
kbackup-v1.1.1-public-trust.zip. Private signing material is not included.Verification
Start with
BUNDLES-SHA256SUMS, then use the platform archive for 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-amd64The DEB and RPM carry native OpenPGP package signatures. The Windows CLI,
daemon, and installer carry SHA-256 Authenticode signatures and critical RFC
3161 timestamps. Windows reports them as trusted only after the self-managed
root and publisher certificates are deliberately enrolled.Key convenience-download SHA-256 values:
kbackup-setup-v1.1.1-x64.exe 0d2dc8738f7f0834368127ab953d53c758d5748d08c049cf9f84ef550e1c77d8 kbackup_1.1.1_amd64.deb b2ad4f68eeed90f673806543b55353dfb9a6c9310db8afc62975dedabb1056dd kbackup-1.1.1-1.x86_64.rpm d071f27463f85dd34e37e8ed2391f58fc94eb8ffc68bb821f6895db6952e7231The exact signed artifacts passed clean disposable-VM acceptance on Windows 11
Enterprise 25H2/NTFS first, followed by Debian 13/ext4. Acceptance covered
signature trust, install and service lifecycle, backup and content-verified
restore, retention, check/scrub/prune, reboot credential reopen, scheduler
corruption and repair, notification failure and saturation, owner web setup,
uninstall data retention, and reinstall/reopen.The supported platform and repository boundaries remain those documented in
docs/support.md.Downloads
- Redesigned the dashboard, repositories, jobs, authentication, and setup
-
kBackup v1.1.0 Stable
released this
2026-07-27 16:04:22 +02:00 | 54 commits to main since this releasekBackup v1.1.0
This is the production-signed v1.1.0 release. The exact tagged source is
3364bbb5eff23ed75c4e55c078606c7f7cf11b26.Changelog
- Added TUI controls for enabling and configuring the web interface.
- Added a simple first-run web setup flow launched from a one-time owner URL
generated by the TUI. - Preserved owner token authentication after initial setup.
- Added web configuration persistence, validation, and service integration.
- Added coverage for web settings, setup tokens, authentication, and setup-page
behavior. - Updated the Web UI and generated protobuf clients.
- Removed generated
web/distfiles from Git; release builds now rebuild and
verify the embedded UI before compiling with thewebdistbuild tag. - Expanded build-artifact and frontend-cache exclusions in
.gitignore. - Removed the hosted CI workflow because this repository does not use hosted
CI.
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 installing the bundled root:405fbb57e597845d2d0f85855bd8df9f5cfad82ec3e54fbdb11cc010fa9dd020Approved production identities:
- Authenticode signer certificate SHA-256:
8edce320469b986ac0ee934bd84b06c98612f6f7e0a8ce228c9a9718ae4960fe - RFC 3161 timestamp certificate SHA-256:
2a19aedf8fa8f61e5851562c354e7d27d0029ad3292510aba8051801675bb3d0 - OpenPGP signing subkey:
D1ED1F306D446FB0F7A3C0BD2B3AA6B27E33386A - Cosign public key SHA-256:
2cb49a5331a5d0fb14347469bf2f4063969069f462d52e3b6ea75451462e5a3d
The complete public bundle is attached as
kbackup-v1.1.0-public-trust.zip. Private signing material is not included.Verification
Start with
BUNDLES-SHA256SUMS, then use the platform archive for 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-amd64The DEB and RPM carry native OpenPGP package signatures. The Windows CLI,
daemon, and installer carry SHA-256 Authenticode signatures and critical
RFC 3161 timestamps. Windows reports them as trusted only after the
self-managed root and publisher certificates are deliberately enrolled.Key convenience-download SHA-256 values:
kbackup-setup-v1.1.0-x64.exe d3910dc4b04734965738b52836356c59db919d6c5f3254afe20c5c95e0c5de07 kbackup_1.1.0_amd64.deb fe3ad8f1784af50edd580f49baf18a971151faf9e9af2544a1b3b48e8b4a1036 kbackup-1.1.0-1.x86_64.rpm 29bec5afb09209a9e61dacb9f93f4c482733feab5ccbbb8ad30ba904526d6560The exact signed artifacts passed clean disposable-VM acceptance on Windows
11 Enterprise 25H2/NTFS first, followed by Debian 13/ext4. Acceptance covered
signature trust, install and service lifecycle, backup and content-verified
restore, retention, check/scrub/prune, reboot credential reopen, owner web
setup link and web load, uninstall data retention, and reinstall/reopen.The supported platform and repository boundaries remain those documented in
docs/support.md.Downloads
-
kBackup v1.0.0
Stablereleased this
2026-07-27 11:33:43 +02:00 | 56 commits to main since this releasekBackup v1.0.0
First production baseline for controlled environments using the kBackup self-managed release trust profile.
Supported profile
- Windows 11 Enterprise 25H2 on NTFS,
amd64 - Debian 13 on ext4,
amd64 - New format-v3 repositories on a durable local-filesystem backend
- One active kBackup host/process per repository
- File-tree backup and restore through local TUI/IPC or the loopback web UI
This release is a clean-install baseline. Repositories created by development builds should be preserved with their matching binary, restored, and backed up into a new v3 repository rather than migrated in place.
The RPM, S3/SFTP backends, raw-device workflows, mounts, rescue media, non-loopback web exposure, other operating systems, and other architectures remain preview or unsupported. See docs/support.md for the complete boundary.
Trust and verification
These artifacts use self-managed signing. Windows does not trust the Authenticode signer publicly by default. Independently authenticate the trust manifest digest, then enroll the supplied root and publisher certificate only in controlled systems:
release-trust.json SHA-256: 405fbb57e597845d2d0f85855bd8df9f5cfad82ec3e54fbdb11cc010fa9dd020Package-signing subkey:
D1ED1F306D446FB0F7A3C0BD2B3AA6B27E33386ACosign public-key SHA-256:
2cb49a5331a5d0fb14347469bf2f4063969069f462d52e3b6ea75451462e5a3dFollow docs/release-trust.md. The platform bundles contain the native artifacts,
SHA256SUMS, SBOMs, provenance, and Cosign bundles with their original filenames.BUNDLES-SHA256SUMSis a transport checksum for the uploaded release assets; authoritative artifact authentication is provided by the native signatures and signed platform metadata inside each bundle.Source commit:
259db0d53e80dadf8d713c5fea57098b6dc0e8cbThe exact signed Windows and Debian artifacts passed clean disposable-VM acceptance before publication.
Downloads
- Windows 11 Enterprise 25H2 on NTFS,