You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
toger5
added
the
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
label
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
The text was updated successfully, but these errors were encountered: