MSC4287: Sharing key backup preference between clients#4287
Conversation
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Co-authored-by: Travis Ralston <travisr@matrix.org>
|
|
||
| ## Security considerations | ||
|
|
||
| Unencrypted account data is under the control of the server, so a malicious |
There was a problem hiding this comment.
Heads up that I tripped over this fairly badly while reviewing; my thought process was: "autoenabling backup sounds scary; warning users sounds even scarier - what would the warning even say?". @tulir pointed out however that in practice current clients enable backup automatically at login - so in practice this doesn't significantly change the attack surface.
Instead, paranoid clients which let the user opt out of backup should warn the user when they are enabling backup whatever the scenario - including at login.
Unsure if this needs to be written up on the MSC, but am commenting it here so I have something to refer back to in future.
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
|
The final comment period, with a disposition to merge, as per the review above, is now complete. |
This is a substantive change, which should not be applied during FCP, so reverting it. This reverts commit 395b98a.
|
Spec PR: matrix-org/matrix-spec#2354 |
Rendered
Implementations:
I am employed by Element and a Matrix community member. This proposal was written and published with my Element client developer hat on.
SCT Stuff:
MSC checklist
FCP tickyboxes