Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
AGPL-3.0 License
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.5...1.31.0
Published by BlackDex 8 months ago
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.4...1.30.5
Published by dani-garcia 8 months ago
⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in the next release.
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.3...1.30.4
Published by dani-garcia 9 months ago
This is a minor release to fix some issues with push notification device registration and docker healthcheck.
⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in the next release.
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.2...1.30.3
Published by dani-garcia 9 months ago
⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in the next release.
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.1...1.30.2
Published by dani-garcia 11 months ago
This is a minor release to fix some issues with the Login with device
feature, and restore the alpine
docker tag that was missing on the latest release.
⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in a future release.
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.0...1.30.1
Published by dani-garcia 12 months ago
⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in a future release.
passkey
support, allowing the browser extensions to store and use your passkeys
, make sure the extension is updated to version 2023.10.0
or newer for passkey support.Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.29.2...1.30.0
Published by dani-garcia about 1 year ago
Minor release to fix an issue forcing user to set amaster password when logging in even when it's already set
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.29.1...1.29.2
Published by dani-garcia over 1 year ago
Minor release to fix some issues with organization API key generation when using PostgreSQL
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.29.0...1.29.1
Published by dani-garcia over 1 year ago
WEBSOCKET_ENABLED
and a separate port anymore.String
to &str
for all Rocket functions and some other fixes by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/3491
v0.5
branch to fix endpoints by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/3502
null
not an empty object by @stefan0xC in https://github.com/dani-garcia/vaultwarden/pull/3513
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.28.1...1.29.0
Published by dani-garcia over 1 year ago
X-Request-Email
as base64url with no padding by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3376
/users/<uuid>/invite/resend
admin api by @nikolaevn in https://github.com/dani-garcia/vaultwarden/pull/3397
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.28.0...1.28.1
Published by dani-garcia over 1 year ago
text/plain
API responses to application/json
by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3124
shrink-to-fit=no
from viewport-meta-tag by @redwerkz in https://github.com/dani-garcia/vaultwarden/pull/3126
arm32v6
-specific tag by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3164
/api/devices/knowndevice
with HTTP header params by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/3329
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.27.0...1.28.0
Published by dani-garcia almost 2 years ago
With this feature enabled, actions occurring inside an organization will be recorded in a log, viewable by organization admins and owners. Check the official documentation to learn more: https://bitwarden.com/help/event-logs/ (Note that the Public API is not yet implemented, so the events are only viewable in the Web Vault)
To enable this feature, set ORG_EVENTS_ENABLED=true
. By default all events will be stored indefinitely, if you want to limit that, you can use the EVENTS_DAYS_RETAIN
option. You can also tune the cleanup schedule with EVENT_CLEANUP_SCHEDULE
.
Enables the creation and use of groups inside an organization. At the moment this is in beta because there are some known issues (https://github.com/dani-garcia/vaultwarden/issues/2989). Still, the more this feature is tested, the faster we will be able to stabilize it.
To enable this feature, set ORG_GROUPS_ENABLED=true
, make sure to make proper backups of your instance before hand.
ROCKET_ADDRESS
into account in the Docker healthcheck by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2844
/devices/knowndevice
endpoint by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/2893
register
endpoint to identity
by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/2920
left_join
by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/2976
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.26.0...1.27.0
Published by dani-garcia about 2 years ago
CreationDate
to cipher response JSON by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2813
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.25.2...1.26.0
Published by dani-garcia over 2 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
An incompatibility between the format in which some Bitwarden clients upload attachments and sends could lead to those uploads being silently corrupted. We believe this is occurring only when using the mobile clients and only on the latest vaultwarden 1.25.1.
To mitigate this issue, we're releasing this quick patch to make any upload that could lead to a corrupted file explicitly return an error, notifying the user of the problem.
We recommend updating as soon as possible, and checking that any recently uploaded attachments can be downloaded and opened correctly (The corrupted uploads will return an error when downloading or download a very small file).
We've also fixed the docker volume check added in 1.25.1, if you previously needed to set I_REALLY_WANT_VOLATILE_STORAGE=true
to start the container, please try again without it, and open an issue if it still won't start.
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.25.1...1.25.2
Published by dani-garcia over 2 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
password_hints_allowed
config option by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2586
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.25.0...1.25.1
Published by dani-garcia over 2 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
/api/{alive,now,version}
endpoints by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2433
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.24.0...1.25.0
Published by dani-garcia over 2 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
Expires
header when caching responses by @RealOrangeOne in https://github.com/dani-garcia/vaultwarden/pull/2182
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.23.1...1.24.0
Published by dani-garcia almost 3 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images will not receive any new updates any longer.
read_only
and hide_passwords
flags by @jjlin in https://github.com/dani-garcia/vaultwarden/pull/2073
Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.23.0...1.23.1
Published by dani-garcia about 3 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images are deprecated and will stop being updated after 1.23.0.
EMERGENCY_ACCESS_ALLOWED=false
/alive
endpoint