BrowserID Key Wrapping: Difference between revisions

BrowserID Key Wrapping (view source)

125 bytes added , 28 March 2012

668

edits

Revision as of 06:46, 19 January 2012 (view source) BenAdida (talk \| contribs) (→‎API and Overall Behavior) ← Older edit		Revision as of 02:13, 28 March 2012 (view source) BenAdida (talk \| contribs) (→‎Further Work) Newer edit →
Line 79:		Line 79:

	Currently, if the user loses their password and must reset it, the user key UK might as well be thrown away, and data encrypted against that key is thus lost for good. In future work, we may evaluate a key escrow mechanism by which the key can be recovered, somehow. This is considered out of scope for now.		Currently, if the user loses their password and must reset it, the user key UK might as well be thrown away, and data encrypted against that key is thus lost for good. In future work, we may evaluate a key escrow mechanism by which the key can be recovered, somehow. This is considered out of scope for now.

			If we do introduce key escrow, we would likely augment the API to explicitly allow escrow for certain keys, and not others: