Hello, I’m hosting a #Vaultwarden server behind #Caddy 2.10 and made the following test:
-
Hello, I’m hosting a #Vaultwarden server behind #Caddy 2.10 and made the following test:
Tuning Caddy to allow only #PQC curves:
tls { curves x25519mlkem768 }
Trying to connect with #Firefox Mac -> OK
Trying to connect with #Bitwarden #android client -> FailWithout the #TLS tuning, the Bitwarden Android client will happily connect to the server.
Is it a problem with the Bitwarden Android client or with Android, or both?
-
Hello, I’m hosting a #Vaultwarden server behind #Caddy 2.10 and made the following test:
Tuning Caddy to allow only #PQC curves:
tls { curves x25519mlkem768 }
Trying to connect with #Firefox Mac -> OK
Trying to connect with #Bitwarden #android client -> FailWithout the #TLS tuning, the Bitwarden Android client will happily connect to the server.
Is it a problem with the Bitwarden Android client or with Android, or both?
Hey @bitwarden , ideas?
️
-
Hey @bitwarden , ideas?
️
@patpro Hey there, this is usually resolved by updating your server, but don't hesitate to reach out to their support channels.
-
@patpro Hey there, this is usually resolved by updating your server, but don't hesitate to reach out to their support channels.
@bitwarden in my setup, the bitwarden client creates a TLS session with the Caddy server only. Caddy acts as a proxy to reach the backend.
Caddy is up to date. -
@bitwarden in my setup, the bitwarden client creates a TLS session with the Caddy server only. Caddy acts as a proxy to reach the backend.
Caddy is up to date.@patpro Thanks for the additional detail, to clarify, please make sure your Vaultwarden server is up to date.