The backup solution powered by Kloset and ptar.
A follow-up to the v1.1.6 authentication changes. Signing in from the Plakar UI now uses the confirmation code flow.
plakar login, so both sign-in paths use the same hardened flow.A security release. Authenticating with `plakar login` now requires a confirmation code typed into the terminal that started it, and the API server stops accepting the previous flow on 18 September 2026.
plakar login authenticates through a hardened flow. The confirmation page
served by the Plakar API displays a code that has to be typed into the
terminal the login was started from, so an authentication request can only be
approved by whoever holds that terminal. This closes phishing attacks that
rely on someone else approving the confirmation.From Friday 18 September 2026, the API rejects authentication requests that do
not use the new flow. Upgrade to v1.1.6 before then to keep plakar login
working.
A security-focused patch release. Plakar now refuses to open an unencrypted Kloset store unless you opt in, plugins are signature-checked at install time, and the HTTP store and server were hardened.
PLAKAR_INSECURE_PLAINTEXT is set in the environment.plakar pkg add -allow-unsigned to opt out.sync no longer hands the peer passphrase down to the peer store connector.fs exporter confines restores to the target directory.insecure=true before it will send auth_token
over plaintext HTTP, and it rejects https to http redirects. Assorted
other protocol hardening landed alongside it.ptar over HTTP was hardened.plakar server -token requires clients to present an Authorization: Bearer
token. Requests are now logged.plakar pkg add and plakar pkg show accept -devel to use the integration
devel tree.http and https stores accept new auth_token, insecure, timeout
and tls_no_verify options, documented in
plakar-store(1).backup reports the real cause of a failure when a packfile temporary file
cannot be created, a full /tmp for instance, instead of a bare cancellation.fs importer opens files with O_NONBLOCK, so a FIFO no longer stalls a
backup.fs exporter restores file permissions, and hardlink restoration is
fixed.tar exporter no longer hands hard-link names over as symlink targets.ls displays the uid and gid recorded in the snapshot instead of resolving
them against the local system.mount sets a valid modification time on the root directory.config rejects invalid configuration names.Import() and Export(),
serializes the context Flags field on the wire, and supports custom
metadata.make install installs the manpages correctly.