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

Consider replacing the Awala Channel Protocol with the Messaging Layer Security (MLS) #100

Closed
gnarea opened this issue Jul 19, 2023 · 1 comment

Comments

@gnarea
Copy link
Member

gnarea commented Jul 19, 2023

See: https://blog.phnx.im/rfc-9420-mls/

For anyone scoffing at me for not integrating MLS from the get-go: MLS and Awala were conceived roughly at the same time, and MLS seemed to too complicated and unstable by the time I needed to write the first line of code. It also would've required more effort than building on top of the Signal protocol and CMS EnvelopedData with BouncyCastle/PKI.js.

@gnarea
Copy link
Member Author

gnarea commented Jan 25, 2024

This makes more sense to consider in the context of #42 because MLS applies to groups only.

@gnarea gnarea closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2024
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