v2.1.2

Revaulter v2.1.2

This release contains bug fixes.

Revaulter v2 is the new major version of Revaulter, adopting a fundamentally different architecture.

‼️ Revaulter v2 is not compatible with v1

Starting from v2, Revaulter uses passkeys (WebAuthn) to encrypt, decrypt, and sign messages. While the underlying architecture remains similar (requests are sent using the Revaulter CLI and are approved via a web browser), operations now happen within the browser using cryptographic keys derived from passkeys (via PRF). Messages between the Revaulter CLI and the browser are encrypted end-to-end (the server is a relay which has no knowledge of the plaintext ever).

Fixes

• Fixed issues that made it not possible to add a secondary passkey in some scenarios

Enhancements

• Updated third-party dependencies

v2.1.1

Revaulter v2.1.1

This release includes more detailed audit logging and other under-the-hood improvements

Revaulter v2 is the new major version of Revaulter, adopting a fundamentally different architecture.

‼️ Revaulter v2 is not compatible with v1

Starting from v2, Revaulter uses passkeys (WebAuthn) to encrypt, decrypt, and sign messages. While the underlying architecture remains similar (requests are sent using the Revaulter CLI and are approved via a web browser), operations now happen within the browser using cryptographic keys derived from passkeys (via PRF). Messages between the Revaulter CLI and the browser are encrypted end-to-end (the server is a relay which has no knowledge of the plaintext ever).

New features

• Audit logs now contain more metadata for requests
• Added a "copy to clipboard" button in the audit log UI to copy long IDs

Enhancements

• Updated third-party dependencies

v2.1.0

Revaulter v2.1.0

This release adds support for Ed25519 keys for signing.

Revaulter v2 is the new major version of Revaulter, adopting a fundamentally different architecture.

‼️ Revaulter v2 is not compatible with v1

Starting from v2, Revaulter uses passkeys (WebAuthn) to encrypt, decrypt, and sign messages. While the underlying architecture remains similar (requests are sent using the Revaulter CLI and are approved via a web browser), operations now happen within the browser using cryptographic keys derived from passkeys (via PRF). Messages between the Revaulter CLI and the browser are encrypted end-to-end (the server is a relay which has no knowledge of the plaintext ever).

New features

• Add support for signing messages with Ed25519 keys (including the pre-hashed Ed25519ph variant)
• Web UI doesn't display the hash of the message being signed anymore

v2.0.1

Revaulter v2.0.1

This is primarily a bugfix release.

Revaulter v2 is the new major version of Revaulter, adopting a fundamentally different architecture.

‼️ Revaulter v2 is not compatible with v1

Starting from v2, Revaulter uses passkeys (WebAuthn) to encrypt, decrypt, and sign messages. While the underlying architecture remains similar (requests are sent using the Revaulter CLI and are approved via a web browser), operations now happen within the browser using cryptographic keys derived from passkeys (via PRF). Messages between the Revaulter CLI and the browser are encrypted end-to-end (the server is a relay which has no knowledge of the plaintext ever).

New features

• Configuring a webhook for notifications is now optional in Revaulter, although recommended

Bug fixes

• The server Docker container now has an ENTRYPOINT pointing to the Revaulter server binary, making it easier to generate backups or perform database migrations
• Fixed Apple touch icon not loaded correctly
• Fixed header displaying incorrectly on mobile devices

v2.0.0

Revaulter v2

Revaulter v2 is the new major version of Revaulter, adopting a fundamentally different architecture.

‼️ Revaulter v2 is not compatible with v1

Starting from v2, Revaulter uses passkeys (WebAuthn) to encrypt, decrypt, and sign messages. While the underlying architecture remains similar (requests are sent using the Revaulter CLI and are approved via a web browser), operations now happen within the browser using cryptographic keys derived from passkeys (via PRF). Messages between the Revaulter CLI and the browser are encrypted end-to-end (the server is a relay which has no knowledge of the plaintext ever).

v1.8.3

This is a maintenance release that updates third-party dependencies. Additionally, it changes the key derivation for secrets in the configuration from using HMAC to HKDF.

v1.8.2

This is a maintenance release that updates dependencies and the Go compiler version.

v1.8.1

This is a bugfix release that fixes a regression introduced in 1.8.0

Fixes:

• Fixed: users may be stuck in a redirection loop due to an incorrect configuration of the updated service worker

v1.8.0

This release is focused on improving the client code, including with some security enhancements for the browser.

New features:

• Requests for client assets now are served with headers optimized for caching and security

Changes:

• Client application is now built with Vite and uses Biome for linting/formatting
• Updated server-side and client-side dependencies

v1.7.0

This is a maintenance release, primarily focused on upgrading dependencies and the frontend toolchain.

Changes:

• Updated frontend code to Svelte 5 and Tailwind 4
• Updated frontend dependencies
• Updated backend dependencies