Update proposals/1219-storing-megolm-keys-serverside.md

Co-Authored-By: aditsachde <23707194+aditsachde@users.noreply.github.com>
pull/977/head
Hubert Chathi 5 years ago committed by GitHub
parent 5799c433fe
commit a6977f19c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -129,7 +129,7 @@ results in 0, and ensure that the total length of the decoded string
is 35 bytes. Clients must then remove the first two bytes and the last byte, is 35 bytes. Clients must then remove the first two bytes and the last byte,
and use the resulting string as the private key to decrypt backups. and use the resulting string as the private key to decrypt backups.
#### Enconding the recovery key for server-side storage via MSC1946 #### Encoding the recovery key for server-side storage via MSC1946
If MSC1946 is used to store the key on the server, it must be stored using the If MSC1946 is used to store the key on the server, it must be stored using the
`account_data` type `m.megolm_backup.v1`. `account_data` type `m.megolm_backup.v1`.

Loading…
Cancel
Save