ZJX 1.28 LOCKWIRE: Ready to Create, Inspect, and Restore

For teams working with logs, telemetry, structured exports and repeated engineering artifacts, storage efficiency is the starting point. An archive also has to fit the work around it. Someone will need one directory back. An automated job will need a clear result. A future restore should not depend on recreating the developer's machine.

LOCKWIRE brings those jobs into one supported workflow. It concentrates on the work around ZJX archives, from choosing the material worth keeping to recovering it when it becomes useful again.

Choose the work, then see what you have

Choose the material before you archive it. Create from a single path or several inputs, use a file list, and include or exclude the material that belongs in the result. Later, member listing shows what is inside without extracting it. Literal and pattern selection carry through to restoration, so recovering a particular set of files does not require publishing the whole tree.

Selection keeps the verification promise intact: the whole archive is checked before selected files are published. Solid archives still decode in full, so this is a practical way to control what gets restored, with a full decoding cost. A dry run checks the destination and decoder readiness before writing the result. Workflow and support contract.

That gives a team a useful sequence: inspect what it has, confirm that restoration is possible, choose the needed members, and restore into a fresh destination.

Restore the files you meant to keep

Get the needed subset back with its supported filesystem details intact. Under its exact Linux profile, LOCKWIRE restores file contents, the directory tree, permission bits and nanosecond modification times. It also preserves supported symbolic links as links, with relative targets that stay inside the archive root.

For trees with ownership, hard-link, sparse-file or extended-attribute requirements, check the full fidelity matrix during evaluation. The supported profile makes that fit a decision you can settle before adopting the tool.

A fresh restore is staged and published with an atomic rename after verification. Scheduled jobs can consume structured results, track progress and request bounded cancellation. Separate publication, cleanup and durability states give an automation system the information it needs to decide what comes next.

Protection comes with the archive

LOCKWIRE includes the native passphrase protection developed in 1.27 CIPHERGLASS. The encrypted boundary covers the internal filenames and metadata as well as the contents. CIPHERGLASS qualified on the preceding release line; 1.28.0 is its first public distribution.

The encryption guide states the operational costs plainly. Unlocking authenticates the complete archive, private temporary storage may contain plaintext, and the outer file size remains visible. These are part of choosing a suitable workflow. The ZJX Brief explains the protection model and points to the release evidence.

Keep restoration within reach

Retain a path back to your data alongside the archive. The package includes a rootless installer and uninstaller, checksums, build provenance and an offline restore guide. Its runtime dependencies are declared. Restoring does not require an account, license-server connection, source checkout or developer toolchain; archives that used external codecs still require their recorded decoders.

The published artifacts were retrieved and checked after release, including a clean installation and restoration. Installed-package qualification also covered two clean Linux userspaces. The release record keeps that evidence inspectable.

The engineering lineage continues from 1.26 RELICWIRE. LOCKWIRE now establishes the supported Linux baseline on which teams can evaluate the whole archive lifecycle.

Bring the retention workflow that matters to your business: the data you keep, the storage budget it consumes, and the files you need back. A scoped, paid evaluation measures ZJX against that data and those restoration requirements. Explore ZJX and discuss an evaluation. This Chronicle is free to read; commercial evaluation and business use follow separately agreed written terms.