Right now each payload object contains an 'encryption' property that points to the symmetric key that can be used to decrypt this object. As of storage version 3, this URL is relative. This can lead to problems if the object's GUID contains slashes. As it turns out, the 'encryption' property is superfluous as the engine already knows this value. We should get rid of the 'encryption' property and just always use the engine's value.
Turns out Fx Home relies on record.encryption.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.