668
edits
BrowserID Key Wrapping: Difference between revisions
→Crypto Preliminaries
| Line 43: | Line 43: | ||
WRAP(wrapper_key, wrapped_key, {key1: val1, key2: val2}) | WRAP(wrapper_key, wrapped_key, {key1: val1, key2: val2}) | ||
=== Communication with BrowserID === | |||
In the diagrams below, communication is shown between two client-side (in-browser) domains: the service and BrowserID. Communication between these two domains is done using postMessage across these origins. The BrowserID implementation will eventually be built-in, thus part of the browser chrome rather than a second content origin. In any case, the communication pattern is asynchronous, <tt>postMessage()</tt> style | |||
=== User Key === | === User Key === | ||