github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-11-10 01:15:13 -06:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #5396] bitwarden android client does not support post quantum x25519mlkem768 curve #77352

New Issue
Closed
opened 2026-05-19 14:06:01 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-19 14:06:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @p4tpr0 on GitHub (Jun 20, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5396

Steps To Reproduce

  1. Set up a Vaultwarden server behind an HTTPS proxy
  2. Setup HTTPS proxy to support only x25519mlkem768 curve

For example with Caddy:

	tls {
		protocols tls1.3
		curves x25519mlkem768
	}
  1. Try to connect to the server with android client

Expected Result

The client connects to the server

Actual Result

The client fails to connect because it can’t achieve TLS handshake:

{"level":"debug","ts":1750256950.7433078,"logger":"http.stdlib","msg":"http: TLS handshake error from A.B.C.D:48030: tls: no key exchanges supported by both client and server"}

Removing the line curves x25519mlkem768 allows the client to connect.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.5.0

What server are you connecting to?

Self-host

Self-host Server Version

irrelevent, the connexion fails between the client and the HTTPS proxy

Environment Details

Tested with:

  • Pixel 9a running GrapheneOS
  • Caddy 2.10 as an HTTPS proxy

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @p4tpr0 on GitHub (Jun 20, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5396 ### Steps To Reproduce 1. Set up a Vaultwarden server behind an HTTPS proxy 2. Setup HTTPS proxy to support only x25519mlkem768 curve For example with Caddy: ``` tls { protocols tls1.3 curves x25519mlkem768 } ``` 3. Try to connect to the server with android client ### Expected Result The client connects to the server ### Actual Result The client fails to connect because it can’t achieve TLS handshake: ``` {"level":"debug","ts":1750256950.7433078,"logger":"http.stdlib","msg":"http: TLS handshake error from A.B.C.D:48030: tls: no key exchanges supported by both client and server"} ``` Removing the line `curves x25519mlkem768` allows the client to connect. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.5.0 ### What server are you connecting to? Self-host ### Self-host Server Version irrelevent, the connexion fails between the client and the HTTPS proxy ### Environment Details Tested with: - Pixel 9a running GrapheneOS - Caddy 2.10 as an HTTPS proxy ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bugapp:password-manager labels 2026-05-19 14:06:02 -05:00
GiteaMirror commented 2026-05-19 14:06:04 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Jun 20, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-22878

<!-- gh-comment-id:2990842004 --> @bitwarden-bot commented on GitHub (Jun 20, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22878
GiteaMirror commented 2026-05-19 14:06:05 -05:00
Author
Owner
Copy Link
Copy Source

@Krychaz commented on GitHub (Jun 20, 2025):

Hello,

It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here:

https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch

Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here:

https://bitwarden.com/help/install-on-premise-linux/

https://bitwarden.com/help/install-and-deploy-offline/

If you would like to know more about a Bitwarden self-hosted setup, I will happily put you in touch with our Sales Team, who will be able to provide you with a trial license. You can also initiate this yourself here:

https://bitwarden.com/help/enterprise-free-trial/

<!-- gh-comment-id:2991166256 --> @Krychaz commented on GitHub (Jun 20, 2025): Hello, It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here: https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here: https://bitwarden.com/help/install-on-premise-linux/ https://bitwarden.com/help/install-and-deploy-offline/ If you would like to know more about a Bitwarden self-hosted setup, I will happily put you in touch with our Sales Team, who will be able to provide you with a trial license. You can also initiate this yourself here: https://bitwarden.com/help/enterprise-free-trial/
GiteaMirror commented 2026-05-19 14:06:06 -05:00
Author
Owner
Copy Link
Copy Source

@p4tpr0 commented on GitHub (Jun 20, 2025):

OK but does your self-hosted option supports post quantum x25519mlkem768 curve?

<!-- gh-comment-id:2991244505 --> @p4tpr0 commented on GitHub (Jun 20, 2025): OK but does your self-hosted option supports post quantum x25519mlkem768 curve?
GiteaMirror commented 2026-05-19 14:06:06 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jun 20, 2025):

@p4tpr0 I'm just another user and don't know if it's there or not. But even if it's not there: this probably wouldn't be a "bug" but a "feature request" then. And only the Bitwarden Community Forum is the place for "feature requests", not GitHub.

<!-- gh-comment-id:2991322943 --> @pamperer562580892423 commented on GitHub (Jun 20, 2025): @p4tpr0 I'm just another user and don't know if it's there or not. But even if it's not there: this probably wouldn't be a "bug" but a "feature request" then. And only the Bitwarden Community Forum is the place for "feature requests", not GitHub.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#77352