Skip to content

wiretap v0.2.10

Choose a tag to compare

@plutack plutack released this 11 Sep 11:13
· 54 commits to main since this release

wiretap v0.2.10

This release turns Settings into a workflow-oriented control surface and
completes project lifecycle management for relay operators.

Settings that follow the way wiretap is used

The previous desktop settings form placed every option in one long page.
Settings now has four focused workspaces:

  • Relay connection for the endpoint, desktop identity, and projects owned
    by this desktop.
  • Capture and delivery for automatic forwarding, local interception, and
    SQLite storage.
  • Interface for desktop readability, title bar behavior, and the TUI theme.
  • Relay server for privileged server administration.

The new navigation remains visible while moving between sections. Configurable
pages show whether there are unsaved changes and keep the save action close at
hand. The layout collapses into compact section tabs for narrow windows.

Complete relay project management

Relay administrators can now add a project path to any existing client from
the GUI. This is independent of client registration, so it does not create a
new client ID or rotate a token.

Each project row supports:

  • Move, which changes the owning client and preserves queued relay history.
  • Delete, which removes that project binding and its queued relay history.
    It does not delete local desktop deliveries or affect another project.

The server overview refreshes after every successful mutation. If the selected
relay and client match the current desktop, wiretap also synchronizes its saved
project list and restarts its tunnel automatically.

The ownership model has not changed: a client may own many projects, and each
project has one owning client. Multiple subscribers for one project remains a
separate future relay-model feature.

Relay API additions

  • PUT /admin/projects/{project} assigns a new project to an existing client.
  • DELETE /admin/projects/{project} deletes a project and its queued relay
    history.

Both routes require the relay admin token. Existing client-authenticated add
and remove routes remain available for a desktop managing its own projects.

Upgrade note

Upgrade wiretap-relay before using the new server-admin Add and Delete
controls. Existing databases, client identities, project bindings, and queued
history require no migration.

Full changelog: v0.2.9...v0.2.10