Confirmed users
632
edits
Loop/Architecture/Context: Difference between revisions
Jump to navigation
Jump to search
→Information Privacy
| Line 18: | Line 18: | ||
Standalone clients receive the room metadata key '''kRm''' in the fragment portion of the URL that was provided to them as the means of joining the room. Upon retrieving the encrypted room context information from the server, they use this '''kRm''' to decode the room context information and display it to the user. | Standalone clients receive the room metadata key '''kRm''' in the fragment portion of the URL that was provided to them as the means of joining the room. Upon retrieving the encrypted room context information from the server, they use this '''kRm''' to decode the room context information and display it to the user. | ||
<center>[[File:Loop- | <center>[[File:Loop-keys2.png|Information flow in Loop key handling]]</center> | ||
Further information on derivation of '''kB''' can be found at [[Identity/AttachedServices/KeyServerProtocol]]. The proposal for creating application specific keys ('''kBr''') was originally made [https://mail.mozilla.org/pipermail/dev-fxacct/2014-December/001260.html on the fxa-dev mailing list], and this proposal re-uses the terminology outlined in that message. | Further information on derivation of '''kB''' can be found at [[Identity/AttachedServices/KeyServerProtocol]]. The proposal for creating application specific keys ('''kBr''') was originally made [https://mail.mozilla.org/pipermail/dev-fxacct/2014-December/001260.html on the fxa-dev mailing list], and this proposal re-uses the terminology outlined in that message. | ||