Confirmed users
632
edits
Loop/Architecture/Context: Difference between revisions
Jump to navigation
Jump to search
→Information Privacy
| Line 20: | Line 20: | ||
<center>[[File:Loop-keys.png|Information flow in Loop key handling]]</center> | <center>[[File:Loop-keys.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]. | 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. | ||
'''''Note: The preceding design is predicated on having the ability to retrieve kB from FxA in time for the initial feature landing. This ability is being tracked [https://github.com/mozilla/fxa-content-server/issues/2088 on the FxA github repo]. If this cannot be done in time, we will need to store room-keys client-side. This is sub-optimal, as it makes it impossible to create a room on one client and view or manipulate information on another.''''' | '''''Note: The preceding design is predicated on having the ability to retrieve kB from FxA in time for the initial feature landing. This ability is being tracked [https://github.com/mozilla/fxa-content-server/issues/2088 on the FxA github repo]. If this cannot be done in time, we will need to store room-keys client-side. This is sub-optimal, as it makes it impossible to create a room on one client and view or manipulate information on another.''''' | ||