Skip to content
Discussion options

You must be logged in to vote

The password is never sent unencrypted. It's hashed by the clients before it is sent to the server.
Then Vaultwarden stores this hashed password in the databases by first hashing it again, currently using PBKDF2 600.000.

The only password which is sent unencrypted is the Vaultwarden Admin backend (/admin) password, but any sys-admin can adjust that anyway.

If you want to rule-out any mitm between the reverse proxy and Vaultwarden, you could add a self-signed cert which lives very long to Vaultwarden, and configure the reverse proxy to accept that cert and connect to Vaultwarden via SSL.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by Andrej553-2
Comment options

You must be logged in to vote
1 reply
@BlackDex
Comment options

BlackDex Nov 3, 2025
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants