Confirmed users
134
edits
BrowserID Key Wrapping: Difference between revisions
Jump to navigation
Jump to search
→What this Means for BrowseID
(→Crypto Preliminaries: technically, since we are MACing the ciphertext, we are doing encrypt-then-mac (as opposed to encrypt-and-mac which is MACing the plaintext)) |
Stomlinson (talk | contribs) |
||
| Line 73: | Line 73: | ||
[[Image:Browserid-userkeys.png]] | [[Image:Browserid-userkeys.png]] | ||
==== What this Means for | ==== What this Means for BrowserID ==== | ||
BrowserID is now storing a (wrapped) user-key per email address. This functionality should move to the identity provider for that email address. BrowserID, as the secondary identity provider, will be the fallback, of course. This means we'll need to define an interface for this key-wrapping interface into an identity provider. We leave that specification to a later date. | BrowserID is now storing a (wrapped) user-key per email address. This functionality should move to the identity provider for that email address. BrowserID, as the secondary identity provider, will be the fallback, of course. This means we'll need to define an interface for this key-wrapping interface into an identity provider. We leave that specification to a later date. | ||