@girish Hello i confirm, the update fix the issue thank you

@necrevistonnezr my installation is quite old - that's correct. Thanks for checking in! @girish , thank you for the doc's reference! Guess it might make sense to stress that during the installation, as well as an offer to increase KDF up to 2 mln (as per Bitwarden docs as well).

@andreasdueren cool! I'm intrigued as to how exactly this will work in practice... will have to have a play around once we've got it in the Cloudron package...

https://bitwarden.com/download/

The package is already out by now.

@necrevistonnezr Thank you for providing this information. It is really nice to know that although I am not a German taxpayer they are watching my back as well. Much appreciated. @joseph And as usual, Cloudron team is on the ball patching quickly so any exposure is minimized. Well done!

Yup, this time it picked it up properly . https://git.cloudron.io/cloudron/vaultwarden-app/-/merge_requests/4

@necrevistonnezr I've been using it for a while now and did not encounter any problems.

@overholt per https://github.com/dani-garcia/vaultwarden/discussions/4707#discussioncomment-10054929 , it's not released yet.

yeah, it asked me for the master password which is nearly half a book long

Thanks, Girish. So if no Yubikey info is provided then it'll use the default Yubico server which works fine. I knew my issue is a time thing but it wouldn't work even after manually syncing the date/time on the new windows PC. It works ONLY if the settings are as shown in the screenshot below. Obviously, replace with your actual timezone but keep "set time zone automatically" as off. Location services are off too. Make sure to sync afterwards. [image: 1719424074639-a1715119-f03e-45b4-8f80-2cdc03fded93-image.png]

This works fine for me . Cloudron has the latest version.

@andreasdueren Good question. I don't know the answer. Is there something similar for Argon2id parameters?

Just to add, I also experienced exactly this too