Recent commits to derivepassphrase.git (62376def08b22866498c75ff95e2a1f4b2f5460e)

Auto-format the CLI messages

2026-04-02T09:46:39+02:00

</pre>

Copy-edit translation files

2026-04-02T09:30:07+02:00

Re-normalize whitespace for the commentary in the German translation
files.

Also add commentary to the NO_UNIX_DOMAIN_SOCKETS and
NO_WINDOWS_NAMED_PIPES warning messages and the NO_AGENT_SUPPORT error
message that indicates that these messages belong together, and their
translations should be similar.
</pre>

Update wishlist

2026-04-01T21:45:52+02:00

</pre>

Merge topic branch 'wishlist-formatting' into master

2026-03-23T22:22:04+01:00

* wishlist-formatting:
  Fix wishlist summary table display with multiple references to other entries
  Update wishlist
</pre>

Fix wishlist summary table display with multiple references to other entries

2026-03-23T22:04:29+01:00

In PuTTY's wishlist entry page, links are kept at their default styling.
A line like

    blocks: pageant-deferred-decrypt pageant-forwarding-path pageant-key-confirm

remains readable because the links are underlined, and thus word
boundaries are clearly discernable.

*Our* wishlist page however uses the standard Material for MkDocs
styling, which does not underline links. As such, it is much more
difficult to discern where one link ends and the next one begins.

We fix this by adding 0.5em whitespace between two adjacent links in the
bug-summary table.  We add a right margin instead of a left one, despite
the shakier browser support, because the table text is left-justified
and the margin would "turn into a text-indent" if there happens to be
a line-break between two such links.
</pre>

Update wishlist

2026-03-23T22:04:18+01:00

</pre>

Merge topic branch 'windows-named-pipes' into master

2026-03-23T18:33:33+01:00

* windows-named-pipes: (61 commits)
  Add a changelog entry for Windows named pipe support
  Update the README for v0.6
  Fix unloading SSH keys in the test suite
  Add more tests for the SSH agent socket provider internals
  Overhaul the SSH key tutorial, also aligning it with the SSH key how-to
  Add a tutorial for using SSH keys with `derivepassphrase vault`
  Update the copyright year to 2026
  Fix a longstanding typo in the Markdown manpage examples
  Update the manpages with respect to SSH agents
  Fix minor formatting errors, linting errors, and typos
  Add tests for explicit SSH agent socket provider selection
  Error out correctly when an invalid SSH agent socket provider is specified
  Support specifying the SSH agent socket provider via CLI or configuration
  Document platform-specific coverage exclusion markers
  Work around non-reentrant SSH agent sockets/clients
  Add more coverage exclusion, with commentary
  Report SSH agent socket providers in `--version` output
  Support aliases in `--version` output (item feature lists)
  Turn the built in SSH agent socket provider names into an enum
  Fix coverage slipups in SSH agent socket provider implementations
  ...
</pre>

Add a changelog entry for Windows named pipe support

2026-03-22T22:32:22+01:00

Also mention the `--ssh-agent-socket-provider` command-line option and
the `vault.ssh-agent-socket-provider` configuration option, and mention
some caveats with the test suite on The Annoying OS.

For developers, also mention related recent changes in the test suite:
non-isolated agents and the PERMITTED_SSH_AGENTS and
NON_REENTRANT_SSH_AGENTS environment variables.
</pre>

Update the README for v0.6

2026-03-22T22:23:38+01:00

Adjust the passages concerning SSH agent support and software
dependencies to accurately reflect the state in (what will later become)
v0.6.

Also fix typos in the page footer and in a previous changelog entry that
we came across while editing the README.
</pre>

Fix unloading SSH keys in the test suite

2026-03-22T13:24:44+01:00

In the `ssh_agent_client_with_test_keys_loaded` test fixture, fix the
unloading of the SSH test keys during fixture teardown.  Previously, the
test keys were persisting in the agent due to a protocol violation in
our request -- the payload should be wrapped in an extra layer of
`SSHAgentClient.string` -- but the fixture either never unloaded keys in
the first place (for isolated agents) or it misinterpreted the resulting
error message as indicating that the key was no longer available in the
agent anyway.

To avoid making such silent errors in the future, we now always unload
keys, even for isolated agents, so that these errors have as high
a chance as possible of triggering non-silently.
</pre>