Skip to content

Sunset Shared Secred encryption option #3188

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

Open
toger5 opened this issue Apr 11, 2025 · 0 comments
Open

Sunset Shared Secred encryption option #3188

toger5 opened this issue Apr 11, 2025 · 0 comments
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@toger5
Copy link
Contributor

toger5 commented Apr 11, 2025

Your use case

What would you like to do?

Remove all code that is related with Shared Secred encryption.

Why would you like to do it?

If to-device key exchange is performant enough to support large calls this would simplify our codebase and make calls more secure.

How would you like to achieve it?

Draft a strategy on how we can leave shared secret encryption. We would need a way to verify users. The invite link would need to contain a join secret so we have an actually more secure system.

Have you considered any alternatives?

Keep shared secret as a long term solution and continue maintaining it.

Additional context

No response

@toger5 toger5 added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

No branches or pull requests

1 participant