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

Add recovery key handling to native crypto to keep element compatibility and support MSC4153 #608

Open
MTRNord opened this issue Oct 9, 2024 · 2 comments · Fixed by #609
Labels
L3 Some Users Likelihood P3 Outrageous / Cannot continue to or start to use Priority level - includes missing documentation leading to same outrage etc T6 Crash Bug causes crash OR data loss

Comments

@MTRNord
Copy link
Collaborator

MTRNord commented Oct 9, 2024

MSC4153 seems to actively break crypto of bots as element's labs implementation has started to block non cross-signed devices from being readable. Tulir pointed out that recovery keys are the way to go here.

See also matrix-org/matrix-spec-proposals#4153 (comment)

This might need a rather timeish fix or workaround to not break people's bots since (having used matrix long enough) element likely will push this down their stable clients way before the MSC is stabilized. :/

@MTRNord MTRNord added L3 Some Users Likelihood P3 Outrageous / Cannot continue to or start to use Priority level - includes missing documentation leading to same outrage etc T5 Major usability Impairs usability in key scenarios. labels Oct 9, 2024
@MTRNord
Copy link
Collaborator Author

MTRNord commented Oct 9, 2024

Currently having this MSC in the labs enabled makes this with a pantalaimon setup:

grafik

It is very likely also causing this on native crypto since we dont take any other steps either.

@Gnuxie
Copy link
Member

Gnuxie commented Oct 9, 2024

💀

@Gnuxie Gnuxie added T6 Crash Bug causes crash OR data loss and removed T5 Major usability Impairs usability in key scenarios. labels Oct 9, 2024
@MTRNord MTRNord reopened this Oct 10, 2024
@MTRNord MTRNord moved this from Done to In progress in Draupnir planning Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L3 Some Users Likelihood P3 Outrageous / Cannot continue to or start to use Priority level - includes missing documentation leading to same outrage etc T6 Crash Bug causes crash OR data loss
Projects
Status: In progress
2 participants