1.30.0

[dani-garcia]

⚠️ 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.

Major changes and New Features

• Added 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.
• Updated web vault to 2023.10.0.
• Fixed crashes in ARMv6 devices
• Fixed crashes when trying to create/edit a cipher in the mobile applications.

What's Changed

• Update Rust and Crates by @BlackDex in Update Rust and Crates #3808
• update web-vault to v2023.8.2 by @stefan0xC in update web-vault to v2023.8.2 #3821
• Fix Login With Device without MasterPassword by @BlackDex in Fix Login With Device without MasterPassword #3831
• Update GitHub Workflow by @BlackDex in Update GitHub Workflow #3910
• Fix arm builds by @BlackDex in Fix arm builds #3911
• Fix typos by @tuhanayim in Fix typos #3959
• csp: rename anonaddy.com to addy.io by @stefan0xC in csp: rename anonaddy.com to addy.io #3950
• filter handlebars logs by @stefan0xC in filter handlebars logs #3859
• Remove unnecessary variable clone by @mvalois in Remove unnecessary variable clone #3981
• README.md: Fix grammar nit by @AndreasHGK in README.md: Fix grammar nit #3965
• Fix small issues by @BlackDex in Fix small issues #3964
• Adds LastActive on /admin/users API route by @mvalois in Adds LastActive on /admin/users API route #3951
• Reopen log file on SIGHUP by @tobiasmboelz in Reopen log file on SIGHUP #3909
• Fix External ID not set during DC Sync by @BlackDex in Fix External ID not set during DC Sync #3804
• New config option disable email change by @admav in New config option disable email change #3986
• 2FA Confirmation Code Email subject line change to fix triggering Google spam blocker by @aureateflux in 2FA Confirmation Code Email subject line change to fix triggering Google spam blocker #3572
• Implement cipher key encryption by @dani-garcia in Implement cipher key encryption #3990
• Container building changes by @BlackDex in Container building changes #3958
• Fix issue with MariaDB/MySQL migrations by @BlackDex in Fix issue with MariaDB/MySQL migrations #3994
• feat: Working passkeys storage by @GeekCornerGH in feat: Working passkeys storage #4025
• ci: add trivy workflow by @mightyBroccoli in ci: add trivy workflow #3997
• Fix importing Bitwarden exports by @BlackDex in Fix importing Bitwarden exports #4030

New Contributors

• @tuhanayim made their first contribution in Fix typos #3959
• @mvalois made their first contribution in Remove unnecessary variable clone #3981
• @AndreasHGK made their first contribution in README.md: Fix grammar nit #3965
• @tobiasmboelz made their first contribution in Reopen log file on SIGHUP #3909
• @admav made their first contribution in New config option disable email change #3986
• @aureateflux made their first contribution in 2FA Confirmation Code Email subject line change to fix triggering Google spam blocker #3572
• @mightyBroccoli made their first contribution in ci: add trivy workflow #3997

Full Changelog: 1.29.2...1.30.0

---

This discussion was created from the release 1.30.0.

[alexdelprete]

Upgraded to 1.30.0 yesterday. Tested passkey creation on google account site: VW saves the passkey correctly, but when logging in, it doesn't find it.

I have browser extension 2023.10.1, is the server version correct for VW 1.30.0?:

[BlackDex]

For Firefox it's released. Not sure which browser you use. But i have no clue to be honest.

[alexdelprete]

I use Thorium/Chrome/Edge. No updates yet.

I checked Firefox: have 10.1 and I checked updates...nothing found. The link to the store confirms it's still 10.1.

[BlackDex]

That is then correct version. v2023.10.x has passkey support for browsers.

[alexdelprete]

That is then correct version. v2023.10.x has passkey support for browsers.

The bug which I posted about (google) is solved in 2023.10.2: https://github.com/bitwarden/clients/releases/tag/browser-v2023.10.2

[alexdelprete]

I'm referring to #4038

[logopk]

Oh I see....

Yet the display is not consistent - isn't it?

[BlackDex]

The display is a bit weird. We used to put the Vaultwarden version there, but since clients use a version check to enable or disable some features we need to provide a Bitwarden compatible version there.

[alexdelprete]

So the version provided there is actually the equivalent, funcionality-wise, of BW server?

[BlackDex]

Sorta yes. But Bitwarden only checks currently if the version of the server is greater then or equal to 2023.9.1. since we do not know if we support all features of the 2023.10.x version, we need to keep on the lower side.

[alexdelprete]

Makes sense. Thanks for the explanation.

[NoseyNick]

Wondering if this was expected to have made it into the vaultwarden/server:alpine docker image yet? ... or did something go wrong with the docker build/release? Or perhaps we are supposed to know this is a vaultwarden/server:testing-alpine image "cos it's a .0 release" or something?
Much appreciated! 🍺 👍

[BlackDex]

Use latest-alpine, there was a bug which didn't updated the alpine tag.

[NoseyNick]

Works, many thanks! ⭐ 🍺 👍