Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

curve25519 used for end-to-end, but not for TLS #3655

Open
nisbet-hubbard opened this issue Dec 28, 2024 · 0 comments
Open

curve25519 used for end-to-end, but not for TLS #3655

nisbet-hubbard opened this issue Dec 28, 2024 · 0 comments

Comments

@nisbet-hubbard
Copy link

Is your feature request related to a problem? Please describe.
I get it that curve25519 is being used for end-to-end encryption, which is good until matrix-org/vodozemac#12 happens. But it’s not being used for TLS.

Describe the solution you'd like
So currently, this is what nginx says when it talks to the client:

prime256v1:secp384r1:secp521r1->prime256v1

If curve25519 was implemented for TLS, X25519 would appear instead.

Describe alternatives you've considered
Even when P256 is used for TLS, the end-to-end algorithm remains intact. So the alternative/status quo is to only use curve25519 in the end-to-end logic.

Additional context
https://spec.matrix.org/unstable/client-server-api/#end-to-end-encryption

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant